Claude Cowork began as Anthropic’s separate workspace for larger, agentic tasks. Since September 16, 2026, Cowork and chat are merging into one Claude experience. The useful distinction is now between answering a question and carrying out an authorized task, not two permanently separate products. Existing projects, skills and connectors carry into the unified experience. Anthropic’s announcement describes a staged rollout, not immediate availability for every account.

Unified Claude: rollout and output tools

Pro and Max receive the unified experience first on web, desktop and mobile over the coming weeks. Team and Free are due to follow; Enterprise administrators receive at least 30 days’ notice before their organizations change. A feature missing from your account during rollout is not proof that a different subscription instantly enables it.

Claude Docs and Slides, plus Design inside conversations, are in beta on paid plans. Users can edit, present, share a link, or export slides as PowerPoint or PDF. Enterprise admins decide when to enable these beta tools. Standalone Claude Design remains available. This adds native document/presentation workflows; it does not establish that every export is publication-ready without review.

How agentic work differs from a chat answer

If you’ve used Claude in the browser, you know the loop: paste context in, get a response, copy it somewhere useful. Cowork breaks that loop entirely.

For the desktop local-file workflow, you grant access to specific folders so the agent can work within that scope. Do not generalize that desktop execution model to every web or mobile task in unified Claude. Anthropic says Claude asks before actions by default; users can configure fewer check-ins while retaining final control. A configurable approval policy is not a guarantee that every phase always requires a separate confirmation.

The task distinction remains useful: an agent can plan and act through authorized tools, while a conversational answer may require no external action. The new product no longer requires choosing a separate Cowork destination to start that task. Local folder permissions still matter for local-file work; do not assume every web or mobile task has unrestricted access to your desktop.

Key Features

Autonomous Multi-Step Execution

Give Claude a goal like “consolidate these twelve meeting notes into a single summary document organized by project.” Define the allowed inputs and desired output, review its plan, and keep approval requirements appropriate to the actions. Check-in behavior depends on the configured policy; inspect the final document rather than equating completed execution with correct content.

Direct File System Access

Cowork reads and writes files natively. It can:

• Scan a folder of invoices and rename them by vendor and date
• Merge multiple CSVs into a single cleaned dataset
• Create new documents from templates
• Reorganize directory structures based on rules you define

All file operations happen within the folders you’ve explicitly permitted. Nothing outside that sandbox is touched.

Computer Control (March 2026)

Anthropic shipped Computer Control in March 2026, giving Cowork the ability to navigate your screen — clicking buttons, filling out form fields, scrolling through spreadsheets, and interacting with desktop applications. This is particularly useful for apps that don’t have APIs or connectors. Cowork can literally see your screen and operate the UI the way you would.

Skills

Skills are reusable action modules — think of them as saved workflows. If you regularly need Cowork to pull data from a spreadsheet, format it, and paste it into a Notion page, you save that as a Skill and trigger it with a single command. Skills can be shared across Projects and with team members.

Scheduled Tasks

Cowork can run tasks on a timer without you being present. Common examples:

• Morning briefings — summarize overnight emails, Slack messages, and calendar changes into a single document on your desktop by 8 AM
• Weekly reports — pull data from connected tools every Friday and generate a formatted summary
• File maintenance — reorganize your Downloads folder nightly

Scheduled Tasks run within Projects (more on those below) and respect the same permission boundaries.

Connectors and Plugins

Cowork ships with 38+ native connectors including Gmail, Slack, Google Drive, Linear, Notion, GitHub, Jira, Salesforce, and more. These let Cowork read from and write to external services without you switching windows.

The plugin ecosystem expanded quickly. Anthropic released 11 official plugins on January 30, followed by 12 role-specific plugins on February 24 covering productivity, sales, finance, HR, engineering, and legal workflows. The plugin launch had a measurable market impact — $285 billion was wiped from software stocks in the days that followed, with Intuit dropping 33%, ServiceNow 23%, and Salesforce 22%. The market’s read: if an AI agent can do what these platforms do from a single desktop interface, the subscription bundles face real pressure.

Cowork vs Claude Code

Cowork and Claude Code share the same underlying engine and were designed for different audiences. In fact, Cowork was built in just 10 days using Claude Code itself.

If you write code for a living, Claude Code is the sharper tool — read the full guide here. If you manage projects, handle documents, or coordinate across tools, Cowork is built for you. Many people use both. For more on the desktop experience, see our Claude Code Desktop redesign guide.

Dispatch: Phone-to-Desktop Control

Rollout distinction: The legacy Dispatch workflow below depends on desktop execution. Anthropic also describes unified Claude tasks continuing after a laptop is closed and progress available by phone. Do not infer that every local-file task runs in the cloud, or apply the older desktop wake requirement to every unified task.

Dispatch lets you send tasks to Cowork from your phone. You’re on the train, you remember you need a report reformatted and emailed before a 9 AM meeting — open Dispatch, type the instruction, and Cowork executes it on your desktop at home (or wherever your machine is running).

Dispatch tasks queue up if your computer is asleep and execute when it wakes. They follow the same permission model — Cowork can only touch folders and connectors you’ve already authorized. It’s a surprisingly natural workflow once you get used to it: your phone becomes a remote control for your desktop agent.

Pricing

One important caveat: Cowork consumes tokens aggressively. Every file it reads, every plan it generates, every connector call — it all counts against your limit. Heavy Pro users regularly hit their ceiling mid-month. If you plan to use Cowork as a daily driver for file management and scheduling, Max ($100/mo) is realistically the floor. For a broader look at how Claude’s models compare to competitors, see our AI model comparison.

Who Should Use Cowork (and Who Shouldn’t)

Cowork is a strong fit if you:

• Spend hours on repetitive file and document tasks (renaming, merging, reformatting)
• Coordinate across multiple tools (email + project management + docs)
• Want scheduled automations without learning Zapier or writing scripts
• Need an assistant that remembers context across sessions (Projects)
• Work in ops, finance, HR, sales, legal, or management roles

Cowork is probably not for you if you:

• Primarily write code (use Claude Code instead)
• Need real-time collaboration with teammates inside the same document
• Need immediate access on Free or Team before the announced follow-on rollout
• Are uncomfortable granting an AI agent file system access, even sandboxed

Projects: The Persistent Workspace

Projects reached general availability in early 2026 and they’re the feature that makes Cowork feel less like a tool and more like a colleague. A Project is a persistent workspace with:

• Memory across sessions — Cowork remembers what you discussed, what files it touched, and what decisions were made. You don’t re-explain context every time you open a conversation.
• Custom instructions — Set per-project rules. “Always use metric units.” “Format dates as DD/MM/YYYY.” “Summarize in bullet points, not paragraphs.”
• Import Chat Projects — Migrate existing Claude chat conversations into a Project. Claude carries over the memory and any referenced files.
• Scheduled Tasks — Attach recurring automations to a Project. Your “Weekly Sales Report” Project can auto-generate every Friday at 5 PM and drop the file in a shared Drive folder.

Projects turn Cowork from a one-shot assistant into something with continuity. For teams, this is where the real productivity gains show up — you build a Project once, refine it over a few sessions, and then it runs reliably on its own.

FAQ

Is Cowork still separate from Claude chat?

It is merging into unified Claude, beginning with Pro and Max on web, desktop and mobile. Team and Free follow later, with Enterprise changes coordinated through administrators. Docs, Slides and in-conversation Design are separate beta capabilities on paid plans, not a promise that every account has already migrated.

Do I need a Max plan for Claude Cowork, or does Pro work?

Pro ($20/mo) includes Cowork access, but heavy users regularly hit their token ceiling mid-month because Cowork consumes tokens aggressively — every file read, plan generated, and connector call counts against your limit. If you plan to use Cowork as a daily driver, Max ($100/mo) is realistically the minimum for uninterrupted usage.

Can Cowork access any file on my computer?

Local-file work requires granting access to the relevant folders. Connected services have their own permissions. Unified Claude is not a claim of unrestricted access to every desktop file from any surface. Review folder grants, connector scopes and the configured approval policy before assigning consequential tasks.

What’s the difference between Cowork and Claude Code for developers?

Claude Code is a terminal-based tool designed for writing and editing code, running tests, and managing Git workflows. Cowork is a GUI desktop agent designed for knowledge workers — file management, email, scheduling, document processing, and cross-tool coordination. Many developers use both: Claude Code for coding and Cowork for everything else (organizing docs, drafting emails, managing project files).

Related Links