[BUG] Telegram plugin: inbound messages not delivered to Claude Code (notifications/claude/channel not received)
Resolved 💬 3 comments Opened Mar 21, 2026 by 0xViolet Closed Mar 25, 2026
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?
The Telegram plugin bot receives inbound messages (confirmed by "typing" indicator appearing in Telegram), but the notifications/claude/channel notification never reaches the Claude Code conversation.
- Outbound works fine:
replytool sends messages successfully - Bot polling works:
getWebhookInfoshowspending_update_count: 0, updates are consumed - Access config is correct: user is in allowlist,
gate()passes (typing indicator fires) - The
mcp.notification()call inhandleInboundexecutes but Claude Code never surfaces the<channel source="telegram">message
Reproduced on v2.1.81 (latest), macOS, Telegram plugin v0.0.1.
What Should Happen?
When an allowlisted Telegram user sends a message, it should appear in the Claude Code conversation as a <channel source="telegram"> message, allowing Claude to read and respond.
Error Messages/Logs
Steps to Reproduce
- Install Telegram plugin: enable
telegram@claude-plugins-officialin settings.json - Configure bot token in
~/.claude/channels/telegram/.env - Pair with a Telegram user (add to allowlist in access.json)
- Start Claude Code (
claudein terminal) - Send a message from the paired Telegram user to the bot
- Bot shows "typing" indicator in Telegram, but the message never appears in the Claude Code conversation
- Outbound
replytool works — Claude can send messages to Telegram successfully
Claude Model
None
Is this a regression?
Yes, this worked in a previous version
Last Working Version
_No response_
Claude Code Version
v2.1.81
Platform
Anthropic API
Operating System
macOS
Terminal/Shell
Terminal.app (macOS)
Additional Information
_No response_
This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗