Remote access

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?

● ## Telegram plugin: inbound MCP notifications not delivered to session

### Summary
The Telegram plugin's bot correctly receives messages and processes them through the gate/allowlist, but
mcp.notification() calls from server.ts never arrive in the Claude Code conversation. Outbound tool calls (reply,
react, edit_message) work fine.

### Environment

• OS: Windows 11 Home 10.0.26200
• Claude Code: latest (as of 2026-03-21)
• Bun: 1.3.11
• Telegram plugin: v0.0.1 (git SHA 61c0597779bd2d670dcd4fbbf37c66aa19eb2ce6)

### Steps to reproduce

1. Install Telegram plugin, configure bot token and access.json (allowlist mode)
2. Start Claude Code session — plugin spawns two bun processes (parent + child server.ts)
3. Send a message from Telegram to the bot

### Expected
Message appears in the Claude Code conversation as a <channel source="telegram" ...> block.

### Actual
Nothing arrives. The conversation never sees the inbound message.

### Debugging done
| Check | Result |
|---|---|
| getWebhookInfo | No webhook set, bot is using long polling |
| getUpdates (manual) | Returns 409 Conflict — confirms bot IS actively polling |
| /status command in Telegram | Bot replies "Paired as 7030104112" — gate/allowlist is correct |
| Outbound reply tool | Works — messages sent successfully (confirmed receipt in Telegram) |
| Bun processes | Both alive (parent PID 80800 → child PID 84892 running server.ts) |
| Restarted Claude Code | No change — same behavior on fresh session |

### Conclusion
The break is between mcp.notification({ method: 'notifications/claude/channel', ... }) in server.ts (line ~792) and the
Claude Code session receiving it. The stdio MCP transport appears to work for tool calls (request/response) but not for
server-initiated notifications.

What Should Happen?

I should be able to access remotely

Error Messages/Logs

Steps to Reproduce

● ## Telegram plugin: inbound MCP notifications not delivered to session

### Summary
The Telegram plugin's bot correctly receives messages and processes them through the gate/allowlist, but
mcp.notification() calls from server.ts never arrive in the Claude Code conversation. Outbound tool calls (reply,
react, edit_message) work fine.

### Environment

• OS: Windows 11 Home 10.0.26200
• Claude Code: latest (as of 2026-03-21)
• Bun: 1.3.11
• Telegram plugin: v0.0.1 (git SHA 61c0597779bd2d670dcd4fbbf37c66aa19eb2ce6)

### Steps to reproduce

1. Install Telegram plugin, configure bot token and access.json (allowlist mode)
2. Start Claude Code session — plugin spawns two bun processes (parent + child server.ts)
3. Send a message from Telegram to the bot

### Expected
Message appears in the Claude Code conversation as a <channel source="telegram" ...> block.

### Actual
Nothing arrives. The conversation never sees the inbound message.

### Debugging done
| Check | Result |
|---|---|
| getWebhookInfo | No webhook set, bot is using long polling |
| getUpdates (manual) | Returns 409 Conflict — confirms bot IS actively polling |
| /status command in Telegram | Bot replies "Paired as 7030104112" — gate/allowlist is correct |
| Outbound reply tool | Works — messages sent successfully (confirmed receipt in Telegram) |
| Bun processes | Both alive (parent PID 80800 → child PID 84892 running server.ts) |
| Restarted Claude Code | No change — same behavior on fresh session |

### Conclusion
The break is between mcp.notification({ method: 'notifications/claude/channel', ... }) in server.ts (line ~792) and the
Claude Code session receiving it. The stdio MCP transport appears to work for tool calls (request/response) but not for
server-initiated notifications.

Claude Model

None

Is this a regression?

Yes, this worked in a previous version

Last Working Version

_No response_

Claude Code Version

2.1.81

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

● ## Telegram plugin: inbound MCP notifications not delivered to session

### Summary
The Telegram plugin's bot correctly receives messages and processes them through the gate/allowlist, but
mcp.notification() calls from server.ts never arrive in the Claude Code conversation. Outbound tool calls (reply,
react, edit_message) work fine.

### Environment

• OS: Windows 11 Home 10.0.26200
• Claude Code: latest (as of 2026-03-21)
• Bun: 1.3.11
• Telegram plugin: v0.0.1 (git SHA 61c0597779bd2d670dcd4fbbf37c66aa19eb2ce6)

### Steps to reproduce

1. Install Telegram plugin, configure bot token and access.json (allowlist mode)
2. Start Claude Code session — plugin spawns two bun processes (parent + child server.ts)
3. Send a message from Telegram to the bot

### Expected
Message appears in the Claude Code conversation as a <channel source="telegram" ...> block.

### Actual
Nothing arrives. The conversation never sees the inbound message.

### Debugging done
| Check | Result |
|---|---|
| getWebhookInfo | No webhook set, bot is using long polling |
| getUpdates (manual) | Returns 409 Conflict — confirms bot IS actively polling |
| /status command in Telegram | Bot replies "Paired as 7030104112" — gate/allowlist is correct |
| Outbound reply tool | Works — messages sent successfully (confirmed receipt in Telegram) |
| Bun processes | Both alive (parent PID 80800 → child PID 84892 running server.ts) |
| Restarted Claude Code | No change — same behavior on fresh session |

### Conclusion
The break is between mcp.notification({ method: 'notifications/claude/channel', ... }) in server.ts (line ~792) and the
Claude Code session receiving it. The stdio MCP transport appears to work for tool calls (request/response) but not for
server-initiated notifications.