claude-code - 💡(How to fix) Fix Telegram/Discord plugin: inbound messages never delivered to session (zombie bun server.ts after restart) [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#50736Fetched 2026-04-20 12:14:29
View on GitHub
Comments
2
Participants
3
Timeline
7
Reactions
0
Author
Timeline (top)
labeled ×3commented ×2subscribed ×1unsubscribed ×1

Fix Action

Fix / Workaround

Workaround: pkill -f "bun server.ts" — Claude Code then restarts clean instances.

Code Example

[sessions-bridge] Session cse_... reconnected successfully
[transport:sdk] attaching SDK bridge (apiBaseUrl=https://api.anthropic.com)
[sessions-bridge] waiting for user message via transport
RAW_BUFFERClick to expand / collapse

Environment

  • Claude Code Desktop, macOS Darwin 25.2.0 (Apple Silicon)
  • telegram@claude-plugins-official v0.0.6
  • discord@claude-plugins-official v0.0.4

Bug 1: Zombie bun server.ts processes after restart

After Claude Code restarts, old server.ts plugin processes survive as orphans, causing 409 Conflict — the new instance cannot poll Telegram/Discord.

ps aux shows multiple competing instances after each restart. The plugin's own source comments acknowledge this risk but the exit logic doesn't reliably clean up.

Workaround: pkill -f "bun server.ts" — Claude Code then restarts clean instances.

Bug 2: Inbound messages not routed to any session

Even with clean processes, inbound messages are never delivered to any Claude Code session. The cse_ session stays in "waiting for user message via transport" indefinitely. No log entries appear in ~/Library/Logs/Claude/main.log when a Telegram/Discord message is sent.

Outbound (Claude → Telegram via reply tool) works correctly.

Reproduction steps

  1. Configure telegram/discord plugin with bot token + allowlist
  2. Send DM to bot → typing indicator appears
  3. No reply is sent
  4. Restart Claude Code → multiple zombie bun server.ts processes appear
  5. Kill zombies → fresh processes start → typing still appears → still no reply

Relevant log entries (~/Library/Logs/Claude/main.log)

[sessions-bridge] Session cse_... reconnected successfully
[transport:sdk] attaching SDK bridge (apiBaseUrl=https://api.anthropic.com)
[sessions-bridge] waiting for user message via transport

No further entries appear when a Telegram/Discord message is sent to the bot.

Additional context

  • Rate limit errors observed during testing: api_error: You've hit your limit
  • No active account/org for marketplace operations on every startup (custom ANTHROPIC_BASE_URL configured)

extent analysis

TL;DR

Killing zombie bun server.ts processes and investigating the message routing issue may resolve the problems with Claude Code's Telegram and Discord plugins.

Guidance

  • Verify that the pkill -f "bun server.ts" workaround effectively removes all zombie processes and allows clean restarts of the plugins.
  • Investigate the message routing issue by checking the plugin's configuration and the cse_ session's status to ensure it's properly connected and waiting for user messages.
  • Review the ~/Library/Logs/Claude/main.log for any errors or warnings related to the Telegram and Discord plugins that might indicate the cause of the message routing issue.
  • Consider the rate limit errors and No active account/org for marketplace operations message as potential contributing factors to the issues.

Example

No code snippet is provided as the issue does not require a specific code change.

Notes

The provided information suggests that there are two separate issues: zombie processes and message routing. Resolving the zombie process issue may not necessarily fix the message routing problem, which requires further investigation.

Recommendation

Apply the workaround pkill -f "bun server.ts" to remove zombie processes and investigate the message routing issue further to identify the root cause and potential solutions.

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…

Still need to ship something?

×6

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

Back to top recommendations

TRENDING