claude-code - 💡(How to fix) Fix Telegram channel plugin MCP connection drops after Bash tool use (macOS Intel) [2 comments, 3 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#51641Fetched 2026-04-22 07:56:48
View on GitHub
Comments
2
Participants
3
Timeline
8
Reactions
0
Timeline (top)
labeled ×6commented ×2

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.

Error Message

Error: No such tool available: mcp__plugin_telegram_telegram__reply

Root Cause

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.

Code Example

claude --channels plugin:telegram@claude-plugins-official --dangerously-skip-permissions --continue

---

Error: No such tool available: mcp__plugin_telegram_telegram__reply
RAW_BUFFERClick to expand / collapse

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

  1. Start Claude Code with the Telegram channel plugin:
    claude --channels plugin:telegram@claude-plugins-official --dangerously-skip-permissions --continue
  2. Send a message via Telegram — Claude receives it and replies successfully
  3. Send 2-3 more messages — all work fine
  4. Send a message that triggers a Bash tool call (e.g., "give me today's date and exact time down to the millisecond")
  5. 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.ppid check) — same crash
  • Swapped bun for Node/tsx as the plugin runtime (modified .mcp.json in 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

extent analysis

TL;DR

The Telegram plugin's MCP connection is likely being terminated due to an issue with how Claude Code manages the connection during Bash tool execution on Intel Macs.

Guidance

  • Investigate the Claude Code's MCP connection management during Bash tool execution to identify the root cause of the disconnection.
  • Verify if the issue is specific to Intel Macs by testing the plugin on a different architecture, such as an M1 Mac or a Linux machine.
  • Check the Claude Code documentation for any known issues or configuration options related to MCP connection management during Bash tool execution.
  • Consider adding logging or debugging statements to the Claude Code or the Telegram plugin to capture more information about the disconnection.

Example

No code snippet is provided as the issue is more related to the interaction between Claude Code and the Telegram plugin, and the root cause is not yet identified.

Notes

The issue may be specific to Intel Macs, and testing on a different architecture may help to confirm this. The fact that the plugin works flawlessly for pure text exchanges and only dies on the first Bash tool invocation suggests that the issue is related to the interaction between Claude Code and the Bash tool execution.

Recommendation

Apply a workaround by testing the plugin on a different architecture, such as an M1 Mac or a Linux machine, to see if the issue is specific to Intel Macs. This may help to identify the root cause of the problem and provide a temporary solution until a fix is available.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

FAQ

Expected behavior

The Telegram plugin MCP connection should survive Bash tool calls.

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

claude-code - 💡(How to fix) Fix Telegram channel plugin MCP connection drops after Bash tool use (macOS Intel) [2 comments, 3 participants]