Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix [BUG] Telegram plugin: inbound MCP channel notifications (notifications/claude/channel) not displayed 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#47924•Fetched 2026-04-15 06:38:28
View on GitHub
Comments
1
Participants
2
Timeline
8
Reactions
0
Author
xiaocai-ai01xiaocai-ai01
Participants
github-actions[bot]github-actions[bot]xiaocai-ai01xiaocai-ai01
Timeline (top)
labeled ×5closed ×1commented ×1unlabeled ×1

Error Message

Error Messages/Logs

notification appears to be sent silently without error, but is never received/displayed by Claude Code.

Code Example

No visible errors. The bot process does not log any failure to stderr when calling mcp.notification(). The
  notification appears to be sent silently without error, but is never received/displayed by Claude Code.
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 receives inbound messages from Telegram users but they never appear in the Claude Code session.
The bot is running, polling is active, and the sender is on the allowlist — but no <channel source="telegram">
notification shows up in the conversation.

Outbound works fine: the reply tool successfully sends messages to Telegram. Only the inbound direction (server →
Claude Code notifications) is broken.

What Should Happen?

When an allowlisted Telegram user sends a message to the bot, it should appear in the active Claude Code session as a <channel source="telegram" chat_id="..." message_id="..." user="..." ts="..."> block, allowing Claude to read and respond to it.

Error Messages/Logs

No visible errors. The bot process does not log any failure to stderr when calling mcp.notification(). The
  notification appears to be sent silently without error, but is never received/displayed by Claude Code.

Steps to Reproduce

  1. Install telegram plugin (telegram@claude-plugins-official 0.0.5)
  2. Configure bot token via /telegram:configure
  3. Pair a Telegram account via /telegram:access pair <code>
  4. Set dmPolicy to "allowlist"
  5. DM the bot from the paired Telegram account
  6. Observe: nothing appears in the Claude Code session
  7. Confirm outbound works: call reply tool → message arrives in Telegram

Claude Model

Opus

Is this a regression?

Yes, this worked in a previous version

Last Working Version

No response

Claude Code Version

2.1.107

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

  • Claude Code version: 2.1.107
    • OS: macOS Darwin 25.3.0
    • Bot process stdio: connected via unix pipes to the claude process (confirmed via lsof)
    • Bot has active TCP connections to Telegram servers (149.154.166.110:443)
    • /reload-plugins and restarting the bot process do not fix the issue
    • MCP capabilities declared: experimental['claude/channel'] and experimental['claude/channel/permission']
    • Tool calls from Claude → bot work correctly (reply, react, edit_message all function)
    • Only server-initiated notifications (bot → Claude Code) are affected

extent analysis

TL;DR

The issue might be related to the Telegram plugin's inbound message handling, and checking the plugin's configuration and the mcp.notification() call could help resolve the issue.

Guidance

  • Verify that the mcp.notification() call is correctly formatted and includes all required parameters, such as source, chat_id, message_id, user, and ts.
  • Check the Telegram plugin's configuration, especially the dmPolicy setting, to ensure it is set to "allowlist" and the paired Telegram account is correctly configured.
  • Investigate the bot process's stdio connection to the Claude process via unix pipes, as confirmed by lsof, to ensure it is functioning correctly.
  • Review the MCP capabilities declared by the bot, specifically experimental['claude/channel'] and experimental['claude/channel/permission'], to ensure they are correctly configured.

Example

No code snippet is provided as the issue does not include specific code details.

Notes

The issue is reported as a regression, and the last working version is not specified. The provided information suggests that the issue is specific to the Telegram plugin and the Claude Code version 2.1.107.

Recommendation

Apply workaround: Investigate the Telegram plugin's configuration and the mcp.notification() call to identify the root cause of the issue, as the problem seems to be related to the inbound message handling.

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#generation error#database connection#vector store#embedding generation

Still need to ship something?

×6

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

Back to top recommendations

TRENDING