[BUG] Telegram inbound messages silently dropped — 2.1.126 + plugin 0.0.6

Resolved 💬 3 comments Opened May 5, 2026 by joeyvansommeren Closed May 5, 2026

Environment

  • Claude Code: 2.1.126
  • Telegram plugin: 0.0.6 (claude-plugins-official marketplace)
  • macOS Darwin 25.4.0
  • Bot token: ~/.claude/channels/telegram/.env
  • access.json: dmPolicy: "allowlist", user Telegram ID on the list

What happened

Sending a message to the bot on Telegram triggers a brief "typing..." indicator, then nothing. The message never appears in the Claude Code conversation. No file lands in inbox/. No stderr output.

Outbound direction works. MCP tools (reply, react) are functional once a chat_id is available. The transport is alive. The message just never arrives upstream.

What I expected

Inbound Telegram messages to appear in the Claude Code conversation, matching the plugin's documented behaviour.

Repro steps

  1. Configure bot token at ~/.claude/channels/telegram/.env.
  2. Add user Telegram ID to access.json allowlist.
  3. Start Claude Code. Confirm bot process is running.
  4. Send any message to the bot from the allowed Telegram account.
  5. Observe: "typing..." appears briefly, then disappears. Nothing lands in Claude Code.

Diagnostics already done

  • ps confirms bot process is running. No zombie pollers, single instance only.
  • lsof confirms TCP connection to Telegram API is established.
  • MCP transport is alive — stdio piped to Unix sockets, verified functional via outbound tool calls.
  • /reload-plugins completed cleanly: \"Reloaded: 9 plugins · 11 skills · 28 agents · 5 hooks · 3 plugin MCP servers\"
  • Called deleteWebhook against Bot API directly — returned \"already deleted\". Webhook conflict ruled out.
  • No errors in stderr at any point during message delivery attempt.
  • The \"typing...\" indicator confirms the bot process receives the update from Telegram. The drop happens between update receipt and Claude Code conversation delivery.

Related issues

This appears to be a recurring pattern across versions. None of the existing reports cite the 2.1.126 + 0.0.6 combination specifically.

  • #37933, #37119, #37256, #36898, #36431, #36503, #46744

View original on GitHub ↗

This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗