Telegram plugin: inbound MCP notifications not delivered on Windows

Summary

The Telegram plugin's inbound message notifications (notifications/claude/channel) are never surfaced in the conversation on Windows, even though outbound tool calls (reply, react, edit) work correctly.

Environment

• Platform: Windows 11 Home 10.0.26200
• Claude Code: CLI
• Plugin: Telegram channel plugin v0.0.4

Steps to reproduce

1. Configure the Telegram plugin with a valid bot token and allowlisted user
2. Send a message from Claude Code to Telegram via the reply tool — works
3. Reply to the bot from Telegram — message never appears in the conversation

Diagnosis

• The bot IS polling Telegram (confirmed via getUpdates returning 409 Conflict when a second consumer is attempted)
• Only one bun process pair is running (no zombie from a previous session)
• access.json has dmPolicy: "allowlist" with the correct user ID in allowFrom
• server.ts calls mcp.notification({ method: 'notifications/claude/channel', ... }) at line 925 after gate approval
• The MCP server's stdio transport is connected (outbound tool calls succeed over the same pipe)
• The notification call includes a .catch() error handler (line 945) — no errors observed on stderr

Expected behavior

Messages sent to the bot by an allowlisted user should appear in the Claude Code conversation as <channel source="telegram" ...> tags.

Actual behavior

Nothing appears. The bot receives and consumes the update (typing indicator fires, ack reaction works if configured), but the MCP notification never reaches the Claude Code client.

🤖 Generated with Claude Code