claude-code - 💡(How to fix) Fix [FEATURE] Detachable/undockable Chat, Cowork, and Code tabs for multi-monitor workflows [1 comments, 2 participants]

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

The Chat, Cowork, and Code tabs are pinned inside a single window. If you're running a long Cowork task and want to simultaneously monitor or interact with a Code session (or vice versa), you can't — you have to keep switching tabs in the same window.

These are tabs. I expect them to behave like tabs — the way Chrome tabs do. I should be able to drag one out to a second monitor and keep working. There's no obvious reason they should be treated differently.

This is already how people work

In practice, I'm already multitasking across tabs. Cowork runs a long autonomous task (research, file processing, document generation), and while it's chugging along, I switch to Code to keep working on something else. When Code hits a multi-minute operation, I switch back to check on Cowork. Back and forth, all session.

The parallelism is already happening — I'm just forced to do it blind, tab-switching to peek at progress instead of having both visible. With a second monitor right there, this feels unnecessarily painful.

Possible performance issue when switching tabs

Anecdotally, it feels like active Code or Cowork sessions slow down or hang when their tab is not in the foreground. I don't have hard evidence, but the pattern is consistent enough to notice: switch away from a running session, come back, and it seems like less progress was made than expected — as if the background tab was deprioritized or paused.

If this is real, detachable windows would sidestep the problem entirely — each tab runs in its own window, nothing is ever "backgrounded" by a tab switch. Even if it's not a real issue, avoiding the shared-window-single-foreground-tab architecture removes the question altogether.

Use Case

• The main one: work in Code while monitoring a long-running Cowork task on a second monitor (or vice versa), without constant tab-switching
• Keep Chat open for quick questions while autonomous work runs in the other tabs
• Avoid potential performance degradation from background tabs
• General multi-monitor productivity — the hardware is there, let us use it

Environment

• macOS / Windows
• Applies to all plan tiers with access to Cowork and Code

Proposed Solution

Option A: Detachable tabs (preferred)

Allow tabs (Chat, Cowork, Code) to be detached/undocked into their own windows, similar to how browser tabs or IDE panels can be torn off and moved to a second monitor.

• Right-click a tab → "Open in new window" or drag-to-detach
• Each detached window maintains its own session state and stays synced
• Closing a detached window docks it back, doesn't kill the session

Alternative Solutions

Option B: Unified interface with multiple instances

There's a related request (#40750) to merge Chat, Cowork, and Code into a single adaptive interface. If that's the direction things are heading — fine, merge them. But the core problem remains: I need to see multiple active sessions side by side.

If it's all one unified thing, then let me open multiple instances of it, each with its own active session. Same outcome: Cowork task running on one monitor, Code session on the other. The underlying architecture (separate tabs vs. unified interface) doesn't matter as long as parallel visibility is supported.

Priority

High - Significant impact on productivity

Feature Category

Other

Use Case Example

• The main one: work in Code while monitoring a long-running Cowork task on a second monitor (or vice versa), without constant tab-switching
• Keep Chat open for quick questions while autonomous work runs in the other tabs
• Avoid potential performance degradation from background tabs
• General multi-monitor productivity — the hardware is there, let us use it

Additional Context

No response