Telegram plugin: inbound MCP notifications not reaching session on Windows
Resolved 💬 3 comments Opened Mar 26, 2026 by eddyficial Closed Mar 29, 2026
Description
The Telegram channel plugin (v0.0.4) receives inbound messages via grammy polling but the MCP notifications (notifications/claude/channel) never reach the Claude Code session. Outbound messaging (reply tool) works fine.
Environment
- Windows 11 Home 10.0.26200
- Claude Code v2.1.83
- Telegram plugin v0.0.4
- Runtime: bun
Steps to reproduce
- Configure Telegram bot token in
~/.claude/channels/telegram/.env - Add sender ID to allowlist in
access.json(dmPolicy: "allowlist") - Reload plugins (
/reload-plugins) - Send a message from Telegram to the bot
Expected behavior
Message appears in the Claude Code session as a channel notification.
Actual behavior
- Bot polls Telegram successfully (confirmed via
getUpdatesafter killing bun) - Messages are received by the bot (verified by pulling updates directly via curl)
notifications/claude/channelis called in server.ts but never surfaces in the session- Outbound replies via the
replyMCP tool work correctly - Two bun processes spawn on reload; the polling slot is always held (409 Conflict on manual getUpdates)
Debugging done
- Verified bot token is valid (
getMereturns correct bot info) - Verified sender ID is on the allowlist
- Killed all bun processes and confirmed messages exist via
getUpdates - Deleted webhook and dropped pending updates
- Multiple plugin reloads attempted
- Switched between
pairingandallowlistpolicies -- no difference
This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗