Telegram channel stops processing inbound messages after completing a turn

Bug Description

When running Claude Code with the Telegram channel (--channels plugin:telegram@claude-plugins-official), the session stops processing new inbound Telegram messages after completing a response turn. Claude returns to the > prompt and sits idle — new messages from Telegram are received by the MCP server but do not trigger a new conversation turn.

The user has to manually type something in the terminal (e.g., press Enter or type a message) to "wake up" the session and get it to process queued Telegram messages.

Steps to Reproduce

1. Launch Claude Code with Telegram channel:

``sh
claude --channels plugin:telegram@claude-plugins-official --dangerously-skip-permissions
``

1. Send a message to the bot in Telegram — Claude responds correctly
2. After Claude finishes responding, it returns to the > prompt
3. Send another message in Telegram
4. Expected: Claude processes the new message and responds
5. Actual: Claude sits idle at > prompt. The message is not processed until the user interacts with the terminal

Environment

• Claude Code v2.1.81
• Model: Opus 4.6 (1M context)
• macOS (Darwin 25.3.0)
• Telegram plugin v0.0.4 (claude-plugins-official)
• Permissions: bypass on (--dangerously-skip-permissions)

Screenshots

Terminal shows Claude completed a reply ("sent (id: 333)"), returned to idle > prompt, and does not react to subsequent Telegram messages (including a forwarded PDF + text messages).

Notes

• This is not a permissions issue — bypass permissions on is active
• The MCP server appears to stay connected (no errors in terminal)
• Messages with attachments (forwarded PDFs) seem especially likely to be missed, but plain text messages are also affected
• The issue is intermittent but frequent enough to make the Telegram channel unreliable for async use

🤖 Generated with Claude Code