claude-code - 💡(How to fix) Fix [FEATURE] Multiple independent chat sessions / tabs in a single window

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…

Fix Action

Fix / Workaround

Use case: running parallel work streams without juggling tmux panes or separate terminal tabs Why it's different from subagents: subagents are dispatched by Claude and report back; you want peer sessions you drive directly UX sketch: keyboard shortcut to switch (Ctrl+Tab?), maybe a tab bar, each session has its own context and history Alternatives considered: tmux, multiple terminal tabs, --agent flag — and why they're worse

RAW_BUFFERClick to expand / collapse

Preflight Checklist

  • I have searched existing requests and this feature hasn't been requested yet
  • This is a single feature request (not multiple features)

Problem Statement

Use case: running parallel work streams without juggling tmux panes or separate terminal tabs Why it's different from subagents: subagents are dispatched by Claude and report back; you want peer sessions you drive directly UX sketch: keyboard shortcut to switch (Ctrl+Tab?), maybe a tab bar, each session has its own context and history Alternatives considered: tmux, multiple terminal tabs, --agent flag — and why they're worse

Proposed Solution

Proposal: Browser-style tabs inside one process.

  • Ctrl+T new tab, Ctrl+Tab switch, Ctrl+W close, Ctrl+1..9 jump
  • Tab bar shows name + status (idle / working / notification)
  • Each tab: own context, history, todos
  • Shared: auth, MCP, skills, agents, settings
  • Background tabs keep running; notification dot when they need attention

Why not tmux: no unified notifications, reloads MCP/state per process, not discoverable, doesn't apply to the IDE/desktop/web variants.

Open questions: per-tab vs shared working dir? Per-tab MCP connections? Persistence across restarts?

Alternative Solutions

No response

Priority

High - Significant impact on productivity

Feature Category

Interactive mode (TUI)

Use Case Example

No response

Additional Context

No response

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 [FEATURE] Multiple independent chat sessions / tabs in a single window