Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix Telegram plugin: inbound channel notifications never surface in Claude Code (outbound works) [1 comments, 2 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#56240•Fetched 2026-05-06 06:33:26
View on GitHub
Comments
1
Participants
2
Timeline
6
Reactions
0
Author
bounce12340bounce12340
Participants
bounce12340bounce12340github-actions[bot]github-actions[bot]
Timeline (top)
labeled ×4commented ×1cross-referenced ×1

The official [email protected] plugin's inbound message flow is broken on Claude Code 2.1.128. The bot receives Telegram messages correctly, but notifications/claude/channel notifications never surface as <channel source="telegram"> blocks in the conversation. Outbound (the reply tool) works fine.

Root Cause

Claude Code 2.1.128 may not implement a handler for the experimental notifications/claude/channel method that the plugin's MCP server emits (server.ts:957). Tool RPCs work because they use standard MCP request/response, but channel notifications are fire-and-forget — without a client-side handler, they're silently dropped.

RAW_BUFFERClick to expand / collapse

Summary

The official [email protected] plugin's inbound message flow is broken on Claude Code 2.1.128. The bot receives Telegram messages correctly, but notifications/claude/channel notifications never surface as <channel source="telegram"> blocks in the conversation. Outbound (the reply tool) works fine.

Environment

  • Claude Code: 2.1.128
  • Plugin: telegram@claude-plugins-official v0.0.6
  • OS: macOS (Darwin 25.4.0)
  • Bot runtime: bun

Reproduction

  1. Install and configure telegram plugin via /telegram:configure
  2. Pair a Telegram user via /telegram:access pair <code> — sender ID added to allowFrom
  3. From Claude Code, call mcp__plugin_telegram_telegram__reply → message arrives on Telegram ✅
  4. From Telegram, send any message back to the bot → nothing happens in Claude Code ❌

Evidence

  • claude mcp list reports plugin:telegram:telegram: ✓ Connected
  • Bot polling confirmed (TCP ESTABLISHED to 149.154.166.110:443)
  • Sender ID present in ~/.claude/channels/telegram/access.json allowFrom
  • Photos sent from Telegram are downloaded to ~/.claude/channels/telegram/inbox/ (proves bot receives messages and gate passes)
  • grep '<channel source="telegram"' across all ~/.claude/projects/-Users-chunghsutsai/*.jsonl returns zero matches — no session has ever received the notification

Hypothesis

Claude Code 2.1.128 may not implement a handler for the experimental notifications/claude/channel method that the plugin's MCP server emits (server.ts:957). Tool RPCs work because they use standard MCP request/response, but channel notifications are fire-and-forget — without a client-side handler, they're silently dropped.

Expected

Telegram messages from allowlisted senders should appear in the active Claude Code session as <channel source="telegram" chat_id="..." ...> user-message blocks.

extent analysis

TL;DR

The issue is likely due to Claude Code 2.1.128 not implementing a handler for the notifications/claude/channel method, causing Telegram messages to be silently dropped.

Guidance

  • Verify that the notifications/claude/channel method is not handled in Claude Code 2.1.128 by checking the codebase for any references to this method.
  • Check the plugin's MCP server code (server.ts:957) to confirm that it emits the notifications/claude/channel method.
  • Investigate if there are any open issues or pull requests related to implementing a handler for this method in Claude Code.
  • Consider reaching out to the Claude Code development team to confirm if this is a known issue and if there are any plans to implement the necessary handler.

Notes

The issue seems to be specific to the notifications/claude/channel method and does not affect standard MCP request/response used by tool RPCs.

Recommendation

Apply workaround: Consider using an older version of Claude Code that may have implemented the necessary handler, or wait for an update that includes the fix.

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…
#agent execution#callback error#memory management#API rate limit#retriever error

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 Telegram plugin: inbound channel notifications never surface in Claude Code (outbound works) [1 comments, 2 participants]