What is Claude Cowork?
Chat answers. Cowork does the job and hands you the file. Anthropic's agentic surface runs in the Claude desktop app on macOS and Windows, reads and writes the folders you connect, calls your connected services, and finishes with a document rather than a reply. It is on every paid plan and not on Free.
No card. 3 free pages, each live for 7 days.
What is Claude Cowork?
Claude Cowork is Anthropic's agentic surface for knowledge work. In the Claude desktop app it reads and writes files in folders you connect, uses connectors and MCP servers, drives a browser, and runs multi-step jobs through to a finished deliverable. It is included on every paid plan, runs on macOS and Windows, and is not part of the Free plan.
What Cowork actually is
Anthropic describes Cowork as the desktop app where Claude works directly with your files and connected tools. That sentence is doing more work than it looks. A chat window is a place to ask; Cowork is a place to hand something over. You describe the outcome, Claude writes a plan, breaks it into subtasks, runs them, and comes back with the artefact at the end.
The practical differences are the ones you feel on day one. Cowork reaches your local files without an upload step. It keeps working through a long job instead of running out of conversation. It can run subtasks in parallel. It can open a browser and click things. And it returns files people actually use: a spreadsheet whose formulas calculate, a deck, a formatted document, a folder that has been sorted and renamed.
What it does, in the order you will meet it
- Reads and writes your folders. Connect a folder and Claude works inside it. Anthropic is clear that it can only read and write where you have granted access.
- Runs long jobs. Cloud sessions keep going when you step away, so a research sweep or a reconciliation does not need you watching it.
- Uses your tools. Connectors and MCP servers put Google Workspace, GitHub, Microsoft 365 and the rest inside the job rather than beside it.
- Takes browser actions. Navigating, clicking and filling forms, in a built-in browser on the desktop app or through Claude in Chrome.
- Asks before it commits. Manual mode pauses for approval on each action. Auto mode runs continuously with safety checks that block unsafe steps. Skip mode asks for nothing and is the fastest.
Who it is for
Cowork is aimed squarely at people who are not going to open a terminal. That is the split with Claude Code, which is the same agentic capability with a command line in front of it. If your work is code, Claude Code fits. If your work produces documents, numbers and decks, Cowork is the surface built for you, and the two are compared side by side in Claude Cowork vs Claude Code.
The sharpest published example of the audience is Claude for Small Business, launched on 15 September 2026 as a Cowork plugin with 43 ready-to-run workflows and connections to 37 eligible partner services including QuickBooks, HubSpot, Shopify, Stripe, Xero, Square, Gusto, Canva and DocuSign. Nobody in that description is a developer. They are owners and operators who want Monday morning to arrive already assembled.
Is Cowork free, and which plans have it?
Cowork is not on the Free plan. It is included on Pro, Max, Team and Enterprise, and Anthropic lists it on the pricing page next to Claude Code on those tiers. Pro is $17 a month billed annually or $20 billed monthly. Max starts at $100 a month. Team is $20 a seat billed annually or $25 monthly, with premium seats at $100 and $125. Enterprise is $20 a seat billed annually plus usage at API rates.
One thing worth planning for: a Cowork job is many model calls, not one, so it draws down your plan's usage faster than a chat reply of the same apparent size. If you intend to run standing workflows every week, size the plan for that rather than for your chat habits.
Mac, Windows, and everywhere else
Cowork is generally available in the Claude desktop app on macOS and Windows for all paid plans. Anthropic's help centre also lists it on the web for Pro, Max and Team, on iOS and Android for those plans, and in the Chrome side panel for Max and Team with Pro rolling out. Enterprise availability on the non-desktop surfaces depends on an administrator turning it on. Some things stay desktop-only, including local MCP servers, which matters if your workflow depends on a server running on your own machine.
What people use it for
The pattern in the published material is the work around the work: the connective tissue rather than the craft. Research sprints that end in a written synthesis. Project updates pulled from several systems into one page. Decks assembled from a quarter of scattered notes. Month-end reconciliation that walks a bank statement against a ledger and writes up the mismatches. Batch file jobs that would otherwise eat an afternoon.
Put another way: Cowork is good at the jobs that are tedious rather than hard, that touch several systems, and that end in a document somebody else has to read. The last part of that sentence is the part most people have not solved yet.
How Cowork differs from Claude chat
Chat and Cowork now live in one place, so the difference is a mode rather than a product. In chat, you upload, you ask, you read the answer, you copy it somewhere. In Cowork, you describe the outcome and approve the plan. Chat's unit of output is a message. Cowork's unit of output is a file on your disk. Everything else follows from that: the folder access, the long sessions, the approval modes, the connectors.
What happens to what Cowork makes
Here is the gap. Cowork is excellent at producing the thing and silent about delivering it. The proposal is written, priced and branded, and then it sits in a folder with your name on the file path. The default next move is to attach it to an email, which is the worst version of the work: the client downloads a file, opens it from their file system, and you have no idea whether they read it. Send a large self-contained HTML file and it may not even arrive, since Gmail caps attachments at 25 MB and mail filters treat HTML attachments with suspicion for good reason.
The step that is missing is a link. Publish the output to a private page, send the URL, and the client opens it in a browser with no account, no download and no sign-up. Put a passcode on it if the numbers are sensitive, or restrict it to their company email domain. See when it was opened. When the call produces changes, run the workflow again and replace the page in place, so the link you already sent shows the new version rather than becoming the wrong one.
That is the whole job of Stacktree, and the step-by-step version for a Cowork deliverable is on sending Cowork output to a client. If you want Claude to publish it for you rather than dragging the file anywhere, Stacktree is an MCP server, and Cowork speaks MCP.
Claude chat vs Claude Cowork
| Criterion | Claude chat | Claude Cowork |
|---|---|---|
| Unit of output | A message you read and copy elsewhere. | A file: spreadsheet, deck, document, folder. |
| Your files | Upload by hand, download by hand. | Reads and writes the folders you connect. |
| Job length | One exchange at a time. | Multi-step, keeps running while you are away. |
| Parallel work | No. | Subtasks run alongside each other. |
| Browser actions | No. | Navigate, click and fill forms. |
| Plugins | Plugins are not used in chat; plugin skills are. | Full plugin support, same packages as Claude Code. |
| Plan | Free plan included. | Paid plans only: Pro, Max, Team, Enterprise. |
| Usage cost of a task | One reply, one cost. | Many steps, so a heavier draw on your plan. |
| Getting the result to a client | Copy and paste. | A file in a folder, and no send step. |
Frequent questions
What is Claude Cowork? +
Is Claude Cowork free? +
How much does Claude Cowork cost? +
What can Claude Cowork do? +
Is Claude Cowork available on Windows? +
What is the difference between Claude Cowork and Claude chat? +
What are the main Claude Cowork use cases? +
Does Claude Cowork have access to all my files? +
How do I send something Cowork made to a client? +
Related guides
- What are Claude Live Artifacts? Access, plans, and the sharing gap A plain reading of Anthropic docs: Claude Live Artifacts are persistent Cowork dashboards that re-query your apps and.
- Claude Cowork vs Claude Code Same engine, two front doors. Which one your work belongs in.
- Claude Cowork plugins and skills What a plugin contains, how to install one, and the Small Business workflows.
- Send Cowork output to a client The step after the workflow: a private link, a passcode, a read receipt.
- Publish HTML from Claude Code The MCP connector, one command and an OAuth sign-in.
- Share a Claude Design privately The same export-then-publish move for Claude Design files.
- Share deliverables with clients Gates, expiry, read receipts and feedback, end to end.
Sources and further reading
- Claude Help Center: Get started with Claude Cowork ↗ Anthropic on what Cowork does, which plans and surfaces have it, and the three approval modes.
- Anthropic: Claude for Small Business ↗ The 15 September 2026 launch post: 43 workflows running inside Cowork, and the integration list.
- Claude: plans and pricing ↗ The plan prices quoted here, and which tiers list Cowork and Claude Code.
- Claude Docs: install plugins ↗ What a plugin can contain, and the fact that plugins run in Cowork and Code but not chat.
Cowork makes it. Send it as a link.
Publish the output to a private page the client opens in a browser, with a passcode if you want one and no account either way.
Sign up free →