Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix Telegram plugin notifications/claude/channel delivered successfully but never surfaced in session [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#48785•Fetched 2026-04-16 06:51:01
View on GitHub
Comments
1
Participants
2
Timeline
5
Reactions
0
Author
INV2025INV2025
Participants
github-actions[bot]github-actions[bot]INV2025INV2025
Timeline (top)
labeled ×4commented ×1

Error Message

  • Added file-based logging to the .catch() and .then() of mcp.notification() in server.ts — delivery succeeds every time, error log never created

Error Messages/Logs

RAW_BUFFERClick to expand / collapse

Preflight Checklist

  • I have searched existing issues and this hasn't been reported yet
  • This is a single bug report (please file separate reports for different bugs)
  • I am using the latest version of Claude Code

What's Wrong?

The Telegram plugin (v0.0.5) receives messages and delivers them via mcp.notification({ method: 'notifications/claude/channel' }) successfully, but Claude Code's session never renders them as <channel source="telegram"> tags. The session sits idle with no indication a message arrived.

Environment: Claude Code 2.1.109, Windows 11, Bun 1.3.11, Plugin claude-plugins-official/telegram/0.0.5

Debugging done:

  • Bot token validated via getMe API call — valid and active
  • No webhook set (polling mode confirmed via getWebhookInfo)
  • Plugin runs correctly standalone (bun run server.ts outputs full JSON for received messages)
  • Killing stale bun.exe processes and reloading plugins did not help
  • Fresh session after kill + reload did not help
  • /reload-plugins does not restart the bun process (PIDs unchanged) — had to manually taskkill and reload
  • Added file-based logging to the .catch() and .then() of mcp.notification() in server.ts — delivery succeeds every time, error log never created
  • claude --debug shows zero output when messages arrive

The break is between the MCP notification delivery (which succeeds) and Claude Code's internal session handler that should render notifications as <channel> tags.

What Should Happen?

When the Telegram plugin delivers a notifications/claude/channel MCP notification, the message should appear in the active Claude Code session as a <channel source="telegram"> tag, and Claude should be able to read and respond to it.

Error Messages/Logs

Steps to Reproduce

  1. Configure Telegram plugin via /telegram:configure with valid bot token
  2. Pair and allowlist a user via /telegram:access
  3. Confirm all MCP servers connected via claude mcp list
  4. Give Claude a prompt to monitor Telegram messages
  5. Send a DM to the bot from the allowlisted Telegram account
  6. Observe: typing indicator fires in Telegram, but no <channel> tag appears in session and Claude reports no messages received

Claude Model

None

Is this a regression?

Yes, this worked in a previous version

Last Working Version

No response

Claude Code Version

2.1.109

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

PowerShell

Additional Information

No response

extent analysis

TL;DR

The issue likely lies in the interaction between the Telegram plugin and Claude Code's session handler, where the plugin successfully delivers notifications but they are not rendered as <channel> tags.

Guidance

  • Verify that the mcp.notification() call is correctly formatted and that the method parameter is set to 'notifications/claude/channel' as expected.
  • Check the Claude Code session handler code to ensure it is properly configured to receive and render notifications from the Telegram plugin.
  • Investigate potential version compatibility issues between the Telegram plugin (v0.0.5) and Claude Code (2.1.109), as the issue is reported as a regression.
  • Review the file-based logging added to the .catch() and .then() of mcp.notification() in server.ts to confirm that the delivery succeeds without errors.

Example

No code snippet is provided as the issue does not contain sufficient code context.

Notes

The issue lacks information on the last working version of Claude Code, which could help in identifying the regression cause. Additionally, the claude --debug output is empty, which might indicate a need for more detailed logging or debugging.

Recommendation

Apply workaround: Temporarily downgrade Claude Code to a previous version where the Telegram plugin functionality was known to work, if possible, to isolate the issue and confirm it's a regression.

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…
#api#tool integration#LLM response#prompt template#agent execution

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 notifications/claude/channel delivered successfully but never surfaced in session [1 comments, 2 participants]