[BUG] Telegram plugin: inbound MCP notifications lost after 409 conflict, not recoverable with /reload-plugins

Preflight Checklist

• [x] I have searched existing issues and this hasn't been reported yet
• [x] This is a single bug report (please file separate reports for different bugs)
• [x] I am using the latest version of Claude Code

What's Wrong?

When two Telegram MCP server processes poll the same bot token simultaneously
(e.g. from a previous session and a current one), a 409 Conflict occurs. After
killing the stale process and reloading plugins, the new MCP server process
starts successfully and outbound tool calls (reply, react, etc.) work fine.
However, inbound notifications/claude/channel notifications are never
delivered to the conversation.

Actual behavior

Inbound notifications are silently dropped. The MCP server process is running
and the bot receives messages (typing indicators fire), but
notifications/claude/channel never surfaces in the conversation. Only a full
exit + relaunch of claude fixes it.

Environment

• Platform: Linux
• Claude Code CLI
• Telegram plugin v0.0.4

What Should Happen?

After /reload-plugins, inbound notifications should be delivered to the active conversation.

Error Messages/Logs

Steps to Reproduce

1. Start a Claude Code session with the Telegram plugin configured
2. Leave that session (or it becomes stale) without killing the Telegram MCP

process

1. Start a new Claude Code session a second Telegram bot process begins

polling, causing 409 conflicts

1. Kill the stale process
2. Run /reload-plugins
3. Send a message to the bot from Telegram
4. Outbound reply tool works, but inbound messages never appear in the

conversation

Claude Model

Opus

Is this a regression?

Yes, this worked in a previous version

Last Working Version

_No response_

Claude Code Version

Claude Code v2.1.92

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

_No response_