Proposal: deprecate Cowork and consolidate its capabilities into Claude Code

Resolved 💬 1 comment Opened Jun 6, 2026 by bopuppy101 Closed Jul 12, 2026

Cowork and Claude Code run the same model and the same agent loop. As a daily Claude Code user, I see no reason to maintain two separate, near-identical interfaces. Forcing users to learn and switch between both fragments the experience for no benefit.

Proposal: wind Cowork down as a standalone product and consolidate its capabilities into Claude Code (see companion request: enhance Claude Code with full Cowork feature parity). Cowork's distinctive functionality — GUI/desktop computer use, browser automation, scheduled/persistent tasks, Dispatch, Projects, live artifact previews — would move into Claude Code rather than living in a second app.

I recognize Cowork currently serves non-technical knowledge workers via a simpler desktop entry point, and that the two products have different security postures (Code unsandboxed with full user permissions; Cowork sandboxed VM driving the live screen). The consolidation should preserve a simple on-ramp and preserve the sandbox boundary as an explicit mode — but it should be one product, not two.

Bottom line: one surface, not two near-identical ones, I will never use co-work, add missing features in cowork to claude code, deprecate cowork.

View original on GitHub ↗

This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗