Claude Cowork
Part 1: Claude Code for the Rest of Your Work
The origin story explains the product
Anthropic's launch-era telling: non-technical teams like Marketing and Data started bypassing Claude's chat interface to use Claude Code, so Anthropic built them a version without the terminal. At launch, Anthropic positioned it as "agentic AI for knowledge work" aimed at tasks that are time-consuming but not technically complex: the gap between a chat answer and a finished deliverable.
Who it's for: researchers, analysts, operations teams, legal professionals, finance teams: people who work with documents, data, and files every day.
Same engine as Claude Code: the desktop app runs the same underlying engine as the CLI; Chat, Cowork, and Code are surfaces over it. What Cowork strips out is the terminal, git worktrees, diff review, and dev-server preview.
From research preview to everywhere in six months
Cowork moved fast. The timeline matters because features you read about in January posts are plan-gated or superseded by the GA behavior.
| Date | Milestone | Scope |
|---|---|---|
| Jan 12, 2026 | Research preview brings Claude Code's agentic engine to the desktop app | macOS · Max plan |
| Jan 16, 2026 | Access expands to Pro | macOS |
| Feb 24–25, 2026 | Connectors (Drive, Gmail, DocuSign, FactSet) + Customize section + scheduled tasks | Connectors: all Cowork users; marketplace/admin: Team & Enterprise |
| Mar 17, 2026 | Dispatch: persistent agent thread (research preview) | Pro & Max |
| Mar 23, 2026 | Computer use (research preview) | Pro & Max |
| Apr 9, 2026 | General availability: Windows joins macOS; enterprise RBAC + spend limits | All paid plans |
| May 13, 2026 | Claude for Small Business launches inside Cowork | - |
| Jul 2026 | Web + mobile expansion; remote sessions beta saves sessions to your account across devices | Rolling out from Max |
Timeline sourced from Anthropic's release notes and announcements.
Part 2: Interface & Getting Started
Setup in four steps
Install the Claude Desktop app. claude.com/download: macOS (Universal), Windows (x64/ARM64), and a Linux beta (apt/.deb for Ubuntu and Debian). Note that computer use is not available on Linux.
Sign in and open the Cowork tab. The desktop app is organized around Chat, Cowork, and Code; since the July 2026 update, Chat and Cowork share one home with unified projects and artifacts.
Scope its access. Pick exactly which folders and which connectors (Gmail, Drive, Slack, Notion, …) this session may touch. Scoping is the primary safety model, so grant the minimum.
Optionally enable computer use. Off by default. Settings → General → Computer use; macOS additionally requires Accessibility and Screen Recording permissions.
Dispatch: the delegation inbox
Dispatch is a persistent conversation with Claude that lives in the Cowork tab: you message it a task and it decides how to handle it. The routing is the clever part: research, documents, and spreadsheet work stay in Cowork, while dev-shaped tasks (bug fixes, dependency updates, tests, PRs) get spawned into a Claude Code session automatically, badged in the Code sidebar, with a push notification to your phone when it finishes or needs approval.
Plan gate: Dispatch requires Pro or Max; it is not available on Team or Enterprise plans. Same for computer use.
What people actually delegate
Anthropic's documented capability set, translated into the tasks vibe coders and their teams hand off daily.
File management
Rename, sort, deduplicate, and surface what matters in messy folders: the classic 'clean up my downloads' delegation.
Documents & research
Structured drafts from scattered notes; research synthesis that lands as a review-ready summary rather than a chat transcript.
Data extraction
Dense documents, receipts, invoices, and screenshots extracted into clean spreadsheets.
Real-time computer execution
Opens apps, fills spreadsheets, navigates your browser. No setup and no passwords handed off; it drives the screen you see, with your per-app approval.
Scheduled tasks
Set recurring work once (the weekly metrics pull, the Friday report refresh) and it runs on schedule. With remote sessions in beta, scheduled tasks run even with no device online.
Dispatch from anywhere
Send tasks from your phone and pick up the results later; the Dispatch panel below covers how routing works.
Part 3: Trust Model & Connectors
The trust model: plan approval + scoped access
Cowork's safety model is deliberately simple: you choose which folders and connectors Claude can access, and with permission settings enabled, Claude shows its plan and waits for your approval before anything significant. Consequential decisions stay with you. (The six granular permission modes you may know from Claude Code belong to the Code tab; Cowork itself keeps the simpler plan-approval model.)
Computer use: per-app approvals, permission tiers
When enabled, the first time Claude touches an app you get an "Allow for this session / Deny" prompt; approvals last the session (30 minutes in Dispatch-spawned sessions). App categories carry fixed permission tiers:
View only
Browsers, trading platforms
Claude can read what's on screen but not interact.
Click only
Terminals, IDEs
Claude can click but the category is fenced from free-form control.
Full control
Everything else
Point, click, type, navigate. First use of each app still needs your per-session approval.
Connectors: MCP with a friendly face
Connectors are Model Context Protocol integrations set up with a few clicks instead of config files; under the hood it is the same protocol Claude Code and Codex use. The Feb 2026 wave added Drive, Gmail, DocuSign, FactSet, and more; July added Microsoft 365 write tools.
Small-business bundle: Claude for Small Business runs inside Cowork: toggle it on, connect your tools, pick the job. It bundles 15 + 15 workflows and skills with QuickBooks, PayPal, HubSpot, Canva, DocuSign, Google Workspace, and Microsoft 365 connectors.
Part 4: Routing Work Between Cowork and Claude Code
The routing table
One question decides it: is the deliverable code, or a document/spreadsheet/organized-something? Code goes to the Code tab; everything else goes to Cowork. Dispatch blurs the line on purpose; it routes for you.
| Task | Route to | Why |
|---|---|---|
| Fix a bug, write tests, open a PR | Claude Code | Developer plumbing: git, diffs, test runners |
| Turn 40 meeting notes into a quarterly report | Cowork | Document synthesis with a deliverable at the end |
| Rename and organize 3,000 photos and PDFs | Cowork | File operations with judgment, no code involved |
| Extract line items from 200 invoices into a sheet | Cowork | Data extraction is a headline capability |
| Refactor the auth module behind a feature flag | Claude Code | Needs worktrees, tests, and review discipline |
| “Pull metrics every Friday into the report template” | Cowork (scheduled) | Recurring, cross-app, deliverable-shaped |
| Dev task arrives while you're away from your desk | Dispatch → Claude Code | Dispatch routes dev work to a Code session automatically |
Limitations & gotchas
For local work, the Claude Desktop app must be running. The July 2026 remote-sessions beta softens this: remote sessions and their files live with your Claude account, continue when you close your laptop, and scheduled tasks can run with no device online.
It operates your actual desktop, and Anthropic's docs explicitly warn about prompt injection from on-screen content: a different trust boundary than Claude Code's sandboxed Bash tool. The research-preview label is still on it for a reason. Scope folders tightly, approve apps deliberately, and don't run it unattended on sensitive screens.
Dispatch and computer use are Pro/Max features, not Team or Enterprise. If a teammate on a Team plan can't see Dispatch, that's why. Usage draws from the same pool as your other Claude surfaces, so a heavy Cowork afternoon shows up in your coding budget.
The Linux desktop app is in beta (apt/.deb for Ubuntu and Debian) with the Chat, Cowork, and Code tabs available, but no computer use. The Code tab on Windows requires Git for Windows. The Cowork web experience (July 2026) is another path where the desktop app is not an option.
Why this matters to a vibe coder specifically
You're the person in your orbit who understands agentic tools. Cowork is the version you can hand to a co-founder, a client, or your own operations backlog without teaching anyone a terminal. Everything the Claude Code module taught you about scoping access and reviewing an agent's plan before it acts applies here unchanged. A concrete example: an office manager can hand Cowork the same invoice pile you'd script your way through with Claude Code, using nothing but two folder grants and a one-sentence goal.
Where to go next: the previous module covers Claude Code, where the same engine exposes the full developer toolchain. Next up is OpenAI Codex, the other side of the agentic-coding market.