Claude Cowork: Overview
| π Languages: English | FranΓ§ais | Π£ΠΊΡΠ°ΡΠ½ΡΡΠΊΠ° πΊπ¦ |
Reading time: ~5 minutes
What is Cowork?
Cowork is Claudeβs agentic desktop feature that extends autonomous AI capabilities to non-technical users through the Claude Desktop app. Instead of terminal commands, Cowork accesses local folders and files directly.
Key Facts
| Aspect | Details |
|---|---|
| Release | Generally available (GA), April 9, 2026 |
| Availability | Pro, Max, Team, and Enterprise subscribers |
| Platform | macOS and Windows (Linux not announced) |
| Built by | ~90% written by Claude itself (source) |
| Focus | File manipulation, organization, document generation |
| Usage limits | Resets every 5 hours; heavy tasks consume quota rapidly |
The Three Tabs: One App for the Whole Team
The Claude Desktop app has three tabs, each designed for a different type of work:
| Tab | For who | What it does |
|---|---|---|
| Chat | Everyone | Conversational Claude, no file access |
| Cowork | Knowledge workers | Autonomous agent for files, docs, reports |
| Code | Developers | Full Claude Code with graphical interface |
All three tabs run under the same subscription (Pro, Max, Teams, or Enterprise). Your developers use the Code tab; you use Cowork. Same app, same invoice.
Collaboration pattern: a developer uses the Code tab to build a feature and update the technical spec β you use Cowork to turn that spec into a client-ready presentation. You can share context between both via a shared CLAUDE.md file in a common folder.
For developers on your team: the Code tab is Claude Code with visual diff review, live app preview, GitHub PR monitoring, and parallel sessions β no terminal required. Full reference: code.claude.com/docs/en/desktop
Relationship to Claude Code
Cowork shares the same backend architecture as Claude Code:
| Shared | Different |
|---|---|
| Same model capabilities | Desktop app vs Terminal |
| Extended thinking | Files only vs full shell |
| Agentic loops | Knowledge workers vs developers |
| Sub-agent architecture | No code execution |
Key difference: Cowork cannot execute arbitrary codeβit manipulates files only.
Who Should Use Cowork?
Good Fit
| Persona | Use Case | Why Cowork |
|---|---|---|
| Project Manager | File organization + status reports | Multi-step automation without coding |
| Data Analyst | Local CSV/Excel β formatted reports | Native Excel formulas output |
| Writer/Editor | Research notes β structured documents | Synthesis across many sources |
| Operations | Receipt screenshots β expense reports | Multi-format input processing |
| Consultant | Client docs β deliverables | Cross-reference and synthesis |
| Researcher | Papers + notes β literature review | Source organization and citation |
Poor Fit (For Now)
| Persona | Limitation | Alternative |
|---|---|---|
| Compliance-heavy workflows | Audit Logs donβt capture Cowork activity (confirmed Anthropic limitation) | Review Enterprise Considerations before use |
| Heavy cloud users | No Google Drive/Dropbox confirmed | Use native cloud apps |
| Anyone needing reliability | Preview = bugs, unexpected behavior | Wait for stable release |
| Code execution needs | Files only, no scripts | Use Claude Code |
| Linux users | macOS and Windows only (Linux not announced) | Wait for platform expansion |
| Heavy daily users | Usage limits reset every 5h; Pro exhausts in ~1-1.5h intensive use | Consider Max tier or batch work |
| VPN users | Cannot work with VPN active (VM routing conflict) | Disconnect VPN or use Claude Code |
Architecture
Local-First Design
βββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββ
β CLAUDE DESKTOP APP β
β ββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββ
β β COWORK ββ
β β βββββββββββββββββββββββββββββββββββββββββββββββββββββββββ
β β β ORCHESTRATOR βββ
β β β β’ Receives user request βββ
β β β β’ Creates execution plan βββ
β β β β’ Coordinates sub-agents βββ
β β ββββββββββββββββββββββββ¬βββββββββββββββββββββββββββββββββ
β β β ββ
β β βββββββββββββββ βββββββββββββββ βββββββββββββββββββ ββ
β β β Sub-Agent 1 β β Sub-Agent 2 β β Sub-Agent 3 β ββ
β β β (Analysis) β β (Transform) β β (Organize) β ββ
β β β β β β β β ββ
β β β β’ Read filesβ β β’ Convert β β β’ Move files β ββ
β β β β’ Extract β β β’ Format β β β’ Create dirs β ββ
β β β β’ Summarize β β β’ Generate β β β’ Rename β ββ
β β ββββββββ¬βββββββ ββββββββ¬βββββββ βββββββββ¬ββββββββββ ββ
β β ββββββββββββββββββ΄ββββββββββββββββββ ββ
β β β ββ
β β βββββββββββββββββββββββββββββββββββββββββββββββββββββββββ
β β β LOCAL FOLDER SANDBOX βββ
β β β ~/Cowork-Workspace/ βββ
β β β βββ input/ (your files) βββ
β β β βββ output/ (generated files) βββ
β β βββββββββββββββββββββββββββββββββββββββββββββββββββββββββ
β ββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββ
β β
β βββββββββββββββββββ β
β β CHROME INTEGRATION β β Web tasks (with explicit action) β
β βββββββββββββββββββ β
βββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββ
Technical Specifications
| Aspect | Details |
|---|---|
| Access model | Local folder sandbox (user grants permission) |
| Cloud connectors | Experimental, unreliable (Gmail, Drive available but inconsistent as of January 2026) |
| Sub-agents | Parallel execution with fresh context per agent |
| Code execution | None β Files only (no scripts, no commands) |
| Browser | Chrome integration for web research tasks |
| Context limit | ~200K tokens (~150-500 pages per session) |
| Output formats | Excel (.xlsx with formulas), PowerPoint, Word, PDF, text, images |
How Sub-Agents Work
- Fresh context β Each sub-agent starts clean (no memory from other agents)
- Parallel execution β Multiple agents can work simultaneously
- Orchestrator coordination β Main agent assembles results
- Scope isolation β Each agent sees only what it needs
This architecture enables complex multi-step workflows while maintaining security boundaries.
What Cowork Cannot Do
Understanding limitations is crucial for effective use:
| Limitation | Implication |
|---|---|
| Execute shell commands | No mkdir, mv, cp via terminal |
| Run scripts | No Python, JavaScript, bash execution |
| Access cloud storage | No direct Google Drive, Dropbox, iCloud |
| Network requests | No API calls, no HTTP requests |
| Persist memory | No cross-session memory (only via files) |
| Access arbitrary folders | Only granted sandbox locations |
Workarounds
| Need | Workaround |
|---|---|
| Cloud files | Download to local workspace first |
| Code execution | Use Claude Code instead |
| Cross-session memory | Save context to a file, reload next session |
| Network data | Use Chrome integration for web research |
Mental Model
Think of Cowork as a highly capable assistant with physical access to one folder:
- Can read any file you put there
- Can create new files in any format
- Can reorganize, rename, transform
- Cannot leave that folder without permission
- Cannot run programs or scripts
- Cannot make network connections directly
This constraint is a feature, not a bug β it creates a safe sandbox for autonomous operation.
Enterprise Validation (Claude Adoption)
With Cowork now generally available (GA since April 9, 2026), Claudeβs underlying capabilities are validated at enterprise scale:
| Company | Results | Context |
|---|---|---|
| TELUS | $90M value, 500K hours saved | Document processing at scale |
| Rakuten | 87.5% reduction in processing time | Knowledge work automation |
| Zapier | 89% employee adoption | Workflow integration |
Relevance to Cowork: These stats are for Claude in general, not Cowork specifically. However, they validate the core AI capabilities that power Coworkβs document processing and autonomous workflows.
What this means for you:
- The AI model works reliably at enterprise scale
- Document understanding and generation are production-ready
- Enterprise-tier controls (role-based access, analytics, OpenTelemetry) launched with GA on April 9, 2026
Next Steps
- Getting Started β Setup and first workflow
- Capabilities β Detailed feature breakdown
- Security β Safe usage practices
| *β Back to Cowork Documentation | Getting Started β* |