[Windows] Telegram channel inbound notifications not received by Claude Code
Resolved 💬 4 comments Opened Mar 23, 2026 by shihzunhao-dev Closed Apr 22, 2026
Description
On Windows 11, the Telegram MCP plugin's inbound notifications/claude/channel is not being received by Claude Code, while outbound (reply/react/edit tools) works perfectly.
Environment
- OS: Windows 11 Home 10.0.26200
- Claude Code: latest
- Shell: bash (Git Bash)
- Telegram plugin: 0.0.1
Steps to Reproduce
- Configure Telegram bot token in
~/.claude/channels/telegram/.env - Add sender ID to
allowFrominaccess.json - Start Claude Code session
- Send a DM to the bot from Telegram
Expected Behavior
- Bot sends ❤️ ack reaction
- Message appears in Claude Code session via
notifications/claude/channel
Actual Behavior
- Bot responds to
/startcommand correctly - Bot can send outbound messages via
replytool (MCP connection works) - Regular text messages ("Hi", "Test") get no ack reaction and no notification delivered to Claude Code
getUpdatesreturns 409 Conflict (confirming MCP server IS polling)- This issue is reproducible across sessions (observed 2026-03-22 and 2026-03-23)
Analysis
- The MCP server's polling loop is running (409 Conflict on manual getUpdates)
- Outbound tools work (reply sends successfully), proving MCP ↔ Claude Code stdio is functional
- The
bot.on('message:text')handler appears to not fire for non-command messages, ORmcp.notification()silently fails - The
/startcommand handler works, but generalmessage:texthandler does not trigger ack reaction or notification
This issue has 4 comments on GitHub. Read the full discussion on GitHub ↗