claude-code - 💡(How to fix) Fix --channels session disconnects when switching to agent view or opening multiple Claude Code sessions

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…

Starting Claude Code CLI with --channels (e.g. for a Telegram MCP connection) and then either (a) switching to agent view in the CLI or (b) opening a second Claude Code CLI session causes the --channels session to break and MCP servers (e.g. Telegram) to disconnect.

Root Cause

  • Switching to agent view disconnects MCP servers mid-session
  • Opening any additional Claude Code CLI session appears to break the --channels session
  • Likely root cause: --channels binds to a single session context; a new session or view switch either steals the connection or creates a conflict
RAW_BUFFERClick to expand / collapse

Summary

Starting Claude Code CLI with --channels (e.g. for a Telegram MCP connection) and then either (a) switching to agent view in the CLI or (b) opening a second Claude Code CLI session causes the --channels session to break and MCP servers (e.g. Telegram) to disconnect.

Steps to Reproduce

  1. Start Claude Code CLI with --channels flag (with at least one MCP server configured, e.g. Telegram)
  2. Either:
    • Switch to agent view in the Claude Code CLI, or
    • Open a second Claude Code CLI session (any terminal window)
  3. Observe that the --channels session breaks and MCP connections drop

Expected Behavior

Switching views or running concurrent CLI sessions should not affect active --channels sessions or cause MCP disconnections.

Actual Behavior

  • Switching to agent view disconnects MCP servers mid-session
  • Opening any additional Claude Code CLI session appears to break the --channels session
  • Likely root cause: --channels binds to a single session context; a new session or view switch either steals the connection or creates a conflict

Environment

  • Claude Code version: 2.1.139
  • OS: Windows 11 Pro 10.0.26200
  • MCP affected: Telegram (plugin:telegram)

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

claude-code - 💡(How to fix) Fix --channels session disconnects when switching to agent view or opening multiple Claude Code sessions