Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix --channels flag prints "Listening for channel messages from …" but does not spawn the channel plugin process (v2.1.126) [2 comments, 2 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#56116•Fetched 2026-05-05 05:57:48
View on GitHub
Comments
2
Participants
2
Timeline
6
Reactions
0
Author
lebraatlebraat
Participants
github-actions[bot]github-actions[bot]lebraatlebraat
Timeline (top)
labeled ×3commented ×2closed ×1

Launching claude --channels plugin:telegram@claude-plugins-official reports "Listening for channel messages from: plugin:telegram@claude-plugins-official" in the UI, but no bun run … start child process is ever spawned. Other MCP servers in the same session (e.g. longterm-memory, telegram-mcp) spawn correctly. The result is a half-alive agent: outbound MCP tool calls (telegram - reply) work, inbound TG messages never reach the input loop.

Root Cause

Launching claude --channels plugin:telegram@claude-plugins-official reports "Listening for channel messages from: plugin:telegram@claude-plugins-official" in the UI, but no bun run … start child process is ever spawned. Other MCP servers in the same session (e.g. longterm-memory, telegram-mcp) spawn correctly. The result is a half-alive agent: outbound MCP tool calls (telegram - reply) work, inbound TG messages never reach the input loop.

Fix Action

Workaround

Running the plugin manually (bun server.ts with stdin held open via fifo) confirms it works standalone — but its MCP notifications go to its stdout, which without claude as parent are not ingested.

RAW_BUFFERClick to expand / collapse

Summary

Launching claude --channels plugin:telegram@claude-plugins-official reports "Listening for channel messages from: plugin:telegram@claude-plugins-official" in the UI, but no bun run … start child process is ever spawned. Other MCP servers in the same session (e.g. longterm-memory, telegram-mcp) spawn correctly. The result is a half-alive agent: outbound MCP tool calls (telegram - reply) work, inbound TG messages never reach the input loop.

Reproduction

  1. Linux, claude-code v2.1.126.
  2. claude --mcp-config <path> --channels plugin:telegram@claude-plugins-official --dangerously-skip-permissions
  3. Observe banner says it's listening.
  4. pstree -p <claude-pid> — no bun run --cwd …/external_plugins/telegram --shell=bun --silent start child.
  5. Send a Telegram message — never delivered.

Expected

A bun run … start grandchild (which then runs bun server.ts) appears as a child of the claude process, as it does in long-running sessions started under earlier point-releases.

Confirmed not to be the cause

  • No stale bot.pid lock at ~/.claude/channels/telegram/bot.pid.
  • ~/.claude/channels/telegram/.env present with valid TELEGRAM_BOT_TOKEN.
  • bun is on PATH and the plugin runs cleanly when invoked directly (bun server.ts polls Telegram and emits MCP notifications to stdout).
  • No errors on stderr.

Workaround

Running the plugin manually (bun server.ts with stdin held open via fifo) confirms it works standalone — but its MCP notifications go to its stdout, which without claude as parent are not ingested.

Environment

  • claude-code 2.1.126
  • Linux 6.8.0-110-generic
  • bun 1.x at ~/.bun/bin/bun
  • Plugin: claude-plugins-official/external_plugins/telegram

extent analysis

TL;DR

The issue can be temporarily worked around by manually running the Telegram plugin with bun server.ts and configuring it to send MCP notifications to the correct destination.

Guidance

  • Verify that the bun executable is correctly configured and accessible in the PATH, as the plugin relies on it to run.
  • Check the ~/.claude/channels/telegram directory for any potential configuration issues or missing files that could prevent the plugin from running correctly.
  • Consider modifying the claude command to include additional logging or debugging options to gain more insight into why the bun run child process is not being spawned.
  • Investigate potential differences in configuration or environment between the working longterm-memory and telegram-mcp servers and the non-working plugin:telegram@claude-plugins-official server.

Example

No code snippet is provided as the issue does not imply a specific code-related fix.

Notes

The issue seems to be related to the specific configuration or environment of the plugin:telegram@claude-plugins-official server, as other servers in the same session are working correctly. Further investigation into the differences between these servers may be necessary to identify the root cause.

Recommendation

Apply workaround: Manually run the Telegram plugin with bun server.ts and configure it to send MCP notifications to the correct destination, as this has been confirmed to work in a standalone environment. This will allow for temporary functionality while the root cause of the issue is further investigated.

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…
#retriever error#indexing error#inference speed#output truncation#response parsing

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 --channels flag prints "Listening for channel messages from …" but does not spawn the channel plugin process (v2.1.126) [2 comments, 2 participants]