claude-code - 💡(How to fix) Fix [BUG] Telegram inbound messages silently dropped — 2.1.126 + plugin 0.0.6 [2 comments, 3 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#56258Fetched 2026-05-06 06:32:57
View on GitHub
Comments
2
Participants
3
Timeline
8
Reactions
0
Timeline (top)
labeled ×5commented ×2closed ×1
RAW_BUFFERClick to expand / collapse

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

extent analysis

TL;DR

The issue might be related to the Telegram plugin or Claude Code configuration, and verifying the plugin's compatibility with the current Claude Code version could be a potential fix.

Guidance

  • Review the Telegram plugin's documentation to ensure it is compatible with Claude Code version 2.1.126.
  • Check the access.json file to confirm that the user Telegram ID is correctly added to the allowlist and the dmPolicy is set to "allowlist".
  • Investigate the related issues (#37933, #37119, #37256, #36898, #36431, #36503, #46744) to see if any of them provide insight into the problem or a potential solution.
  • Consider testing the Telegram plugin with a different Claude Code version to isolate the issue.

Example

No code snippet is provided as the issue does not explicitly mention any code-related problems.

Notes

The issue seems to be a recurring pattern across versions, and none of the existing reports cite the 2.1.126 + 0.0.6 combination specifically, which might indicate a compatibility issue.

Recommendation

Apply workaround: Verify the compatibility of the Telegram plugin with the current Claude Code version and test with a different version if necessary, as the issue might be related to a version-specific bug.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

claude-code - 💡(How to fix) Fix [BUG] Telegram inbound messages silently dropped — 2.1.126 + plugin 0.0.6 [2 comments, 3 participants]