Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix Channels plugin: inbound notifications not surfaced to session [1 comments, 1 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#45548•Fetched 2026-04-09 08:02:49
View on GitHub
Comments
1
Participants
1
Timeline
6
Reactions
0
Author
onelowxbonelowxb
Participants
onelowxbonelowxb
Timeline (top)
labeled ×5commented ×1

Code Example

[2026-04-09T02:48:39.574Z] from=XXXXXXX chat=XXXXXXX text=Test123
  gate=deliver
  sending notification for: Test123
  notification sent OK
RAW_BUFFERClick to expand / collapse

Bug

Telegram channel plugin receives inbound messages, passes gate/access control, and the MCP notifications/claude/channel notification resolves successfully (notification sent OK in debug.log) — but the message is never surfaced to the model in the active session.

Outbound works fine — calling the reply tool from the session successfully sends messages to Telegram.

Environment

  • Claude Code v2.1.94 and v2.1.97 (tested both)
  • Windows 11 Pro
  • Telegram plugin v0.0.4 (official, from claude-plugins-official)
  • Plugin loads correctly, tools are available (reply, react, edit_message, download_attachment)

Steps to reproduce

  1. Enable Telegram plugin, start claude session
  2. Verify plugin is connected (telegram tools appear in tool list)
  3. Send a message from Telegram to the bot
  4. Bot receives message, gate=deliver, notification sent OK (confirmed via debug.log at ~/.claude/channels/telegram/debug.log)
  5. Expected: Message appears in session as <channel source="telegram" ...> tag
  6. Actual: Nothing happens. Session never sees the message.

Debug log showing successful delivery

[2026-04-09T02:48:39.574Z] from=XXXXXXX chat=XXXXXXX text=Test123
  gate=deliver
  sending notification for: Test123
  notification sent OK

Additional context

  • This worked earlier in the day on the same version (v2.1.94), then stopped
  • Fresh sessions exhibit the same behavior — not a stale session issue
  • No zombie bun processes — both bun PIDs started at the same time as the session
  • The mcp.notification() promise resolves, meaning the JSON-RPC notification was written to stdout successfully
  • Claude Code just isn't reading/processing those notifications from the MCP stdio transport

extent analysis

TL;DR

The issue may be resolved by investigating the stdio transport between the MCP and Claude Code, as the notification is being sent successfully but not being processed by Claude Code.

Guidance

  • Verify that the mcp.notification() promise resolution is correctly triggering the processing of the notification in Claude Code.
  • Check the Claude Code documentation to ensure that the stdio transport is properly configured and that there are no known issues with the version being used (v2.1.94 and v2.1.97).
  • Investigate the possibility of a timing issue, as the problem started occurring after it had previously worked, and see if there are any logs or indicators that could point to a synchronization problem.
  • Review the debug logs for any other errors or warnings that may be related to the processing of notifications from the MCP.

Example

No code snippet is provided as the issue does not explicitly mention a specific code-related problem.

Notes

The fact that the mcp.notification() promise resolves successfully suggests that the issue lies in the processing of the notification by Claude Code, rather than in the sending of the notification itself. The problem may be specific to the interaction between the MCP and Claude Code, and further investigation into this area is needed.

Recommendation

Apply workaround: Investigate and potentially modify the stdio transport configuration or the notification processing code in Claude Code to ensure that notifications are being correctly received and processed. This is recommended because the issue seems to be related to the interaction between the MCP and Claude Code, and modifying the configuration or code may resolve the problem.

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…
#model save/load#optimization#mixed precision#training loop#device allocation

Still need to ship something?

×6

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

Back to top recommendations

TRENDING