Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix [BUG] Telegram plugin inbound messages not delivered as <channel> tags (v2.1.114)

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…

Error Message

Error Messages/Logs

No error messages. The process tree is healthy, grammY has an ESTABLISHED TCP connection to Telegram API (149.154.166.110:443), and stdio pipes between bun server.ts and

Code Example

No error messages. The process tree is healthy, grammY has an ESTABLISHED TCP connection to Telegram API (149.154.166.110:443), and stdio pipes between bun server.ts and
  ▎ Claude are intact. mcp.notification() is called in handleInbound() but the notification never arrives in the session.
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?

Inbound Telegram messages are never delivered as <channel source="telegram"> tags in the Claude Code session. Outbound (reply tool) works correctly.

What Should Happen?

When a Telegram message is received from an allowlisted user, it should appear as a <channel source="telegram" ...> tag in the active session, prompting Claude to respond

Error Messages/Logs

No error messages. The process tree is healthy, grammY has an ESTABLISHED TCP connection to Telegram API (149.154.166.110:443), and stdio pipes between bun server.ts and
  ▎ Claude are intact. mcp.notification() is called in handleInbound() but the notification never arrives in the session.

Steps to Reproduce

▎ 1. Enable telegram@claude-plugins-official plugin ▎ 2. Pair a Telegram user (add to allowFrom in access.json) ▎ 3. Start a Claude Code session — confirm bun server.ts is running ▎ 4. Send a text message from the paired Telegram account ▎ 5. No <channel> tag appears in the session

Claude Model

Sonnet (default)

Is this a regression?

Yes, this worked in a previous version

Last Working Version

Prior to 2026-04-20

Claude Code Version

2.1.114

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

iTerm2

Additional Information

No response

extent analysis

TL;DR

The issue might be resolved by investigating the mcp.notification() call in the handleInbound() function to ensure the notification is being properly sent and received.

Guidance

  • Review the handleInbound() function to verify that mcp.notification() is being called correctly and that the notification is being sent to the correct destination.
  • Check the access.json file to ensure that the paired Telegram user is correctly configured in the allowFrom section.
  • Investigate the network connection between the Claude Code server and the Telegram API to ensure that there are no issues with the TCP connection.
  • Consider adding logging or debugging statements to the handleInbound() function to gain more insight into the issue.

Example

No code snippet is provided as the issue does not contain sufficient information to create a specific example.

Notes

The issue is reported as a regression, and the last working version was prior to 2026-04-20. This suggests that a change introduced after this date may be the cause of the issue.

Recommendation

Apply workaround: Investigate the handleInbound() function and the network connection to identify the root cause of the issue, as the problem is likely related to the notification not being properly sent or received.

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#file not found#serialization error#model compatibility#GPU setup

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 plugin inbound messages not delivered as <channel> tags (v2.1.114)