The short version: Claude Cowork is a Claude Desktop feature for multi-step knowledge work. It is available on paid Claude plans: Pro, Max, Team, and Enterprise. It works on macOS and Windows, requires the desktop app, can use connected local files, can run code in an isolated VM, and can produce documents, spreadsheets, presentations, organized files, and research summaries.
- Claude Cowork is available on Claude Desktop for macOS and Windows.
- Cowork requires a paid Claude plan: Pro, Max, Team, or Enterprise.
- Cowork is not available as a web-only feature.
- The desktop app must stay open and the computer must stay awake while tasks run.
- Claude can read and write local files in folders you connect.
- Code and shell commands run in an isolated Linux VM on the device.
- Projects in Cowork can store related tasks, files, links, instructions, and memory.
- Cowork activity is not captured in audit logs, the Compliance API, or data exports.
Claude Cowork is Anthropic's attempt to move Claude from "answer this" to "go do this." The current official docs describe it as Claude Code's agentic architecture brought into Claude Desktop for knowledge work beyond coding.
The old version of this article said Cowork was Mac-only, Pro/Max-only, and could not use Projects. That is no longer correct. Anthropic now lists macOS and Windows support, paid-plan availability across Pro, Max, Team, and Enterprise, and Projects built into Cowork.
What is Claude Cowork?
A desktop agent for knowledge work.
Claude Cowork lets you describe an outcome and have Claude work through the steps in Claude Desktop. Anthropic's examples include formatted documents, organized files, synthesized research, spreadsheets, presentations, scheduled tasks, and project workspaces.
The important difference is that Cowork can take actions. Regular chat can explain how to organize a folder. Cowork can organize files in a connected folder. Regular chat can draft a spreadsheet structure. Cowork can create a spreadsheet file with formulas.
Plain-English definition
Claude Cowork is Claude Desktop plus agent tools: local file access, planning, code execution, plugins, projects, scheduling, and longer-running task work.
How Cowork works
The architecture in Anthropic's current docs.
Cowork uses two execution environments on your device. The agent loop runs natively on the device for conversation handling, local file reads and writes in connected folders, web fetches, and local plugin MCP servers. Code execution runs inside a dedicated Linux virtual machine, isolated from the host operating system through Apple Virtualization.framework on macOS or Hyper-V on Windows.
| Part | What Anthropic says it does |
|---|---|
| Agent loop | Handles the conversation, connected-folder file access, web fetches, and local plugin MCP servers. |
| Code execution | Runs shell commands and code inside an isolated Linux VM. |
| Permissions | Uses connected-folder rules, network egress settings, MCP permissions, and Cowork permission modes. |
| Deletion protection | Requires explicit permission before permanently deleting files. |
| Desktop dependency | Tasks need Claude Desktop open, and scheduled tasks need the computer awake. |
This matters because Cowork can touch local files you connect. It can also use browser access, connected services, apps, MCPs, and plugins, depending on what you enable.
What Cowork can do
Current capabilities from the official docs.
| Capability | What it means in practice |
|---|---|
| Direct local file access | Claude can read from and write to connected local folders without manual uploads and downloads. |
| Sub-agent coordination | Claude can split complex work into smaller tasks and coordinate parallel workstreams. |
| Professional outputs | Claude can generate documents, Excel spreadsheets, PowerPoint presentations, reports, and charts. |
| Long-running tasks | Cowork can work on extended tasks without the usual chat rhythm of one reply at a time. |
| Scheduled tasks | You can create tasks that run on demand or on a cadence while the desktop app is open. |
| Projects | Related tasks can live in workspaces with their own files, links, instructions, and memory. |
| Plugins | Plugins can bundle skills, connectors, and sub-agents for specific work. |
| Mobile handoff | Anthropic lists mobile access for Pro and Max users, with Claude working on the desktop while you message from the phone. |
Cowork vs Claude Chat
When chat is enough and when Cowork makes sense.
Not sure which AI model to use?
12 models · Personalized picks · 60 seconds
| Area | Claude Chat | Claude Cowork |
|---|---|---|
| Interaction | One prompt and response at a time | Multi-step task execution |
| Files | Manual uploads and downloads | Connected local folders |
| Outputs | Mostly answers and drafts | Documents, spreadsheets, presentations, organized files, and reports |
| Runtime | Shorter chat turns | Extended tasks that can run while you monitor or step away |
| Scheduling | No Cowork-style scheduled task runner | Scheduled tasks are available in Cowork |
| Risk | Lower, because it mostly replies | Higher, because it can act on files, apps, web content, and connected tools |
Use chat for advice, writing help, quick analysis, and simple file questions. Use Cowork when the task needs file access, multiple steps, repeat runs, or a finished artifact.
Cowork vs Claude Code
Same family, different interface.
Anthropic says Cowork brings Claude Code's agentic capabilities to Claude Desktop for knowledge work beyond coding. Claude Code still belongs in the terminal. Cowork belongs in desktop workflows where the output is a spreadsheet, deck, report, folder cleanup, or recurring research task.
| Area | Claude Code | Claude Cowork |
|---|---|---|
| Interface | Terminal and developer tooling | Claude Desktop |
| Best fit | Software engineering work | Knowledge work, files, documents, research, and office outputs |
| User comfort | Better for users comfortable with repos and command lines | Better for users who want a desktop task interface |
| File work | Codebase-centered | Connected folders and desktop workflows |
| Related guide | Read the Claude Code guide for coding work | Read the Cowork setup guide for first-task steps |
If your work is mostly code, read our Claude Code guide. If your work is a mix of documents, data, files, and research, Cowork is the more relevant starting point.
What can you do with Cowork?
Examples that match Anthropic's docs.
| Use case | Example |
|---|---|
| File management | Organize a Downloads folder by type and date, or batch rename files with a consistent pattern. |
| Receipts and expenses | Process receipts into a formatted expense report. |
| Research synthesis | Combine web searches, articles, papers, and notes into a report or summary. |
| Transcript analysis | Extract themes, decisions, and action items from meeting notes or interview transcripts. |
| Spreadsheets | Generate Excel files with formulas, tabs, formatting, and charts. |
| Presentations | Create slide decks from rough notes or meeting transcripts. |
| Data work | Clean, transform, analyze, and visualize datasets. |
| Recurring work | Schedule repeat tasks that run when Claude Desktop is open and your computer is awake. |
For the exact setup flow, use our Claude Cowork setup guide.
Requirements
What you need before using Cowork.
| Requirement | Current official guidance |
|---|---|
| Plan | Claude Pro, Max, Team, or Enterprise. |
| App | Claude Desktop for macOS or Claude Desktop for Windows. |
| Windows | Requires the latest Claude for Windows app. |
| Web/mobile | Cowork itself requires desktop. Pro and Max users can message Claude from mobile while the desktop does the work. |
| Internet | An active connection is required during the session. |
| App state | Claude Desktop must stay open while Claude works. |
| Computer state | Scheduled tasks run only while the computer is awake and Claude Desktop is open. |
Current limitations
What the docs still warn about.
- Cowork is a desktop feature, not a web-only feature.
- Session sharing is not available for Cowork sessions.
- Memory is supported within Projects, not across standalone Cowork sessions.
- Active tasks can stop if Claude Desktop closes or the computer goes to sleep.
- Scheduled tasks only run while your computer is awake and Claude Desktop is open.
- Cowork activity is not captured in audit logs, the Compliance API, or data exports.
- OpenTelemetry can stream Cowork events for Team and Enterprise owners, but it does not replace audit logging.
- Conversation history is stored locally on users' computers and cannot be centrally exported by admins.
The enterprise caveat is serious
Anthropic says not to use Cowork for regulated workloads that require audit trails. That is not a small footnote if your company has compliance obligations.
Safety considerations
How to think about the risk.
Cowork is useful because it can act. That is also why it needs more care than chat. Anthropic warns that Cowork has unique risks because of its agentic nature and internet access, and says prompt injection risk is not zero even with safety measures.
The practical rule is simple: do not give Cowork broad access on the first run. Start with a dedicated folder, low-risk files, and "Ask before acting." Watch for unexpected file access, unexpected websites, unrelated requests, or task scope creep.
- Avoid connecting folders with financial documents, credentials, personal records, legal files, or customer data.
- Keep backups of important files before letting Cowork edit them.
- Limit browser and web access to trusted sources.
- Use trusted MCPs and plugins only.
- Be careful with Claude in Chrome and computer use, especially around sensitive accounts.
- Do not schedule tasks that send messages, make purchases, publish content, or change production systems.
- Stop the task if Claude accesses unexpected files or websites.
You are still responsible
Anthropic says you remain responsible for actions Claude takes on your behalf, including content published, messages sent, purchases, data accessed or modified, scheduled task actions, and computer use.
Team and Enterprise notes
Admin controls, plugins, and compliance limits.
For Team and Enterprise plans, Anthropic describes Cowork as a research preview. It is on by default when the preview launches, but organization owners can disable it in Organization settings. Team plans have an organization-wide toggle. Enterprise admins can use groups and custom roles for more selective enablement.
| Area | Official note |
|---|---|
| Admin toggle | Owners can enable or disable Cowork in Organization settings. |
| Plugins | Plugins are included with Cowork and controlled by the same admin toggle. |
| Plugin marketplaces | Owners can curate plugins as installed by default, available, required, or not available. |
| Projects | Available to all Cowork users, with no separate org-level project creation control listed for Team plans. |
| Monitoring | Team and Enterprise owners can use OpenTelemetry to stream Cowork events, but it does not replace audit logging. |
| Audit and exports | Cowork activity is not captured in audit logs, the Compliance API, or data exports. |
| Device controls | MDM keys can disable local MCP servers and desktop extensions on managed devices. |
That means Cowork may be fine for internal low-risk productivity work, but it needs a real rollout plan before a company points it at regulated files, customer data, or sensitive systems.
Official sources checked
The Claude and Anthropic docs used for this update.
- Claude Help Center: Get started with Claude Cowork
- Claude Help Center: Use Claude Cowork safely
- Claude Help Center: Use Claude Cowork on Team and Enterprise plans
- Claude Help Center: Claude Cowork desktop architecture overview
The closest comparison is still Manus AI, but Cowork is different because it sits inside Claude Desktop and works with local desktop resources you connect. For tool selection beyond Cowork, use the AI Model Picker.
Keep Reading
Stay ahead of the AI curve
We test new AI tools every week and share honest results. Join our newsletter.