Telegram channel plugin MCP connection drops after Bash tool use (macOS Intel)
Resolved 💬 4 comments Opened Apr 21, 2026 by unwantedburger Closed May 23, 2026
Description
The official Telegram channel plugin (telegram@claude-plugins-official) loses its MCP connection immediately after a Bash tool call. The plugin subprocess dies silently — no error output, no crash log. Messages received before the first Bash call work perfectly; the disconnect is reproducible every time.
Reproduction steps
- Start Claude Code with the Telegram channel plugin:
``bash``
claude --channels plugin:telegram@claude-plugins-official --dangerously-skip-permissions --continue
- Send a message via Telegram — Claude receives it and replies successfully
- Send 2-3 more messages — all work fine
- Send a message that triggers a Bash tool call (e.g., "give me today's date and exact time down to the millisecond")
- Claude runs the Bash command successfully, but when it tries to reply via the plugin, the MCP connection is gone:
````
Error: No such tool available: mcp__plugin_telegram_telegram__reply
What I've tried
- Commented out the orphan watchdog (server.ts lines 657-664, the
process.ppidcheck) — same crash - Swapped bun for Node/tsx as the plugin runtime (modified
.mcp.jsonin the plugin cache) — same crash - Both confirm the issue is not in the plugin's shutdown logic or bun specifically — it's in how Claude Code manages the MCP connection during Bash tool execution.
Expected behavior
The Telegram plugin MCP connection should survive Bash tool calls.
Environment
- Claude Code: 2.1.98
- macOS 14.3.1 (Sonoma)
- Hardware: MacBook Pro 2019, Intel Core i7-9750H (x86_64)
- Bun: 1.3.13 (latest available for Intel Mac)
- Node: v25.9.0
- Plugin version: 0.0.6 (
telegram@claude-plugins-official)
Notes
- A friend running the same plugin on Linux reports no issues — this may be Intel Mac-specific
- The plugin works flawlessly for pure text exchanges (no tool calls). It consistently dies on the first Bash tool invocation
- No error output appears in the terminal when the plugin disconnects — it's completely silent
This issue has 4 comments on GitHub. Read the full discussion on GitHub ↗