[BUG] Telegram plugin inbound messages not delivered as <channel> tags (v2.1.114)

Preflight Checklist

• [x] I have searched existing issues and this hasn't been reported yet
• [x] This is a single bug report (please file separate reports for different bugs)
• [x] 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_