[FEATURE] Split view Chat + Cowork — dual monitor / side-by-side support

Preflight Checklist

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

Problem Statement

Allow users to view Chat and Cowork simultaneously, either as detachable windows or a split-panel layout within Claude Desktop. This enables a "think + execute" parallel workflow that is currently blocked by the single-tab design.

Use Case

We run a complex project (LIA-Factory) involving PowerShell scripting, Windows deployment tooling, and a persistent knowledge base (Weaviate vector DB via MCP). Our validated workflow is:

• Chat → strategic thinking, architecture decisions, planning, code review
• Cowork → long-running execution tasks (500+ line script generation, WinPE ISO builds, WinForms UI generation)

Today we successfully ran both in parallel: Chat on claude.ai web while Cowork executed a WinPE build + WinForms GUI generator (~450 lines) on Claude Desktop. The results confirmed that Chat and Cowork serve fundamentally different roles that complement each other — one is reflective, the other is executive.

However, within Claude Desktop itself, we cannot see both at once. We must tab-switch between Chat and Cowork, losing visual continuity on whichever panel we leave.

Current Limitation

• Claude Desktop uses a single-tab interface: Chat OR Cowork, never both visible simultaneously
• Switching tabs interrupts the current reading/thinking flow
• No way to monitor Cowork progress while composing in Chat
• On dual-monitor setups (increasingly common for knowledge workers), the second screen is wasted

Why This Matters

Cowork is marketed for long-running autonomous tasks where users can "step away and come back to finished work." But in practice, users don't just step away — they continue thinking, planning, and iterating in Chat while Cowork executes. The current tab-switch design forces a false choice: either monitor execution OR continue the strategic conversation.

For dual-monitor users (which Anthropic's target enterprise audience overwhelmingly are), this is a significant missed opportunity. The hardware is there, the workflow is validated, only the UI constrains it.

Environment

Proposed Solution

One or more of the following:

1. Detachable windows: Allow Chat and Cowork tabs to be dragged out into separate OS-level windows, one per monitor
2. Split panel: A vertical or horizontal split within Claude Desktop showing Chat on one side, Cowork on the other
3. Multiple instances: Allow two Claude Desktop instances — one locked to Chat, one to Cowork — sharing the same session/account

Option 1 (detachable windows) would be the most flexible and align with how VS Code, browser DevTools, and most professional tools handle multi-panel workflows.

Alternative Solutions

_No response_

Priority

Medium - Would be very helpful

Feature Category

Interactive mode (TUI)

Use Case Example

Cowork is marketed for long-running autonomous tasks where users can "step away and come back to finished work." But in practice, users don't just step away — they continue thinking, planning, and iterating in Chat while Cowork executes. The current tab-switch design forces a false choice: either monitor execution OR continue the strategic conversation.

For dual-monitor users (which Anthropic's target enterprise audience overwhelmingly are), this is a significant missed opportunity. The hardware is there, the workflow is validated, only the UI constrains it.

Additional Context

• Claude Desktop v1.1.4328.0 (Windows, MSIX)
• Windows 11 Pro 25H2 (Build 26200)
• Dual monitor setup
• Plan: Max