Telegram plugin silently drops inbound messages

Summary

Inbound messages from Telegram are silently dropped intermittently. Outbound messages (reply tool → Telegram) work 100% of the time. The user sends a message to the bot, it never arrives in the conversation, and there is no error or indication of failure on either side.

Reproduction

1. Configure the Telegram channel plugin
2. Send messages from Telegram to the bot during an active CLI session
3. Some messages are silently lost — never delivered to the conversation

Evidence

• Telegram message IDs confirm messages were sent but never received. In one case, IDs jumped from 76 → 80 (at least one message lost in the gap). In another, a message sent at 20:01 was completely lost.
• Outbound replies via reply tool work consistently every time.
• The pattern may correlate with concurrent CLI activity — messages sent while Claude is mid-response to a terminal interaction seem more likely to be dropped. Messages sent while Claude is idle and waiting tend to arrive.

Expected behavior

All inbound Telegram messages should be delivered to the conversation, or at minimum queued and delivered after the current turn completes.

Actual behavior

Messages are silently swallowed. No error on the Telegram side (message shows as sent/delivered), no error in the CLI session. The user has no way to know the message was lost except by the lack of response.

Environment

• macOS (Darwin 25.3.0)
• Telegram plugin v0.0.2
• Claude Code CLI session with remote-control enabled