Claude Cowork vs Claude Code vs Chat: Which to Use

Use Claude Code when the work lives in a code repository: features, bug fixes, tests, scripts and anything that ends in a commit. Use Claude Cowork when you want to hand Claude a multi-step task across your files, connected apps and browser and get a finished deliverable back. Use chat for questions and drafts you steer turn by turn. On 16 September 2026 Anthropic began merging Cowork and chat into one app, Pro and Max first. Claude Code stays separate.

We implement Claude for client teams and run Claude Code in our own operations. Every product fact below was checked against Anthropic's own pages on 29 September 2026.

What is the difference between Claude Code and Claude Cowork?

They share an engine and differ in where the work lives. Anthropic's help center says Cowork "uses the same agentic architecture that powers Claude Code, with no terminal required." Both can take a goal, plan the steps, run them and show you what they did. The difference is what each one is built to work on.

Claude Code is an agentic coding tool. In Anthropic's words it "reads your codebase, edits files, runs commands, and integrates with your development tools." It runs in the terminal, in VS Code and JetBrains, in the Code tab of the Claude desktop app, and on the web at claude.ai/code. It works with git directly: it stages changes, writes commit messages, opens pull requests and can run in CI through GitHub Actions or GitLab.

Claude Cowork is for handing off a task. Claude reads, edits and creates files in the folders you connect, uses your connectors and a built-in browser, runs code in an isolated environment, and delivers a finished output for you to review. Anthropic's product page aims it at marketers building reports, finance teams reconciling data, legal teams reviewing contracts and sales teams working through call notes.

A practical test: if the result of the task is a change to a codebase, use Claude Code. If the result is a document, a spreadsheet, a deck or a set of updated records, use Cowork.

Claude chat vs Cowork vs Code: side-by-side comparison

Sources: claude.com/pricing, Get started with Claude Cowork, Cowork architecture overview, Claude Code overview. All checked 29 September 2026.

Claude chat vs Cowork: are they still separate?

On Pro and Max, they are becoming one product. Anthropic's 16 September 2026 announcement, Claude Cowork and chat are now one Claude, says the two "are merging into one Claude." The stated reason is that users found it frustrating to decide where a task belonged, and work started in one place did not carry into the other. Claude now works out what a task needs, so Cowork's capabilities are available from any conversation, with the same connectors and skills.

The rollout is staged:

• Pro and Max: rolling out over the coming weeks in the Claude app on web, desktop and mobile. Nothing to turn on.
• Team and Free: "will follow soon."
• Enterprise: admins will hear from Anthropic "at least 30 days before anything changes for their organizations."

For most business teams on Team or Enterprise, chat and Cowork are still separate today, and the admin toggles described below still apply. Plan the training for the merge now. Once it lands, people who only ever asked Claude questions can start handing it tasks from the same window, and Anthropic's own guidance is that multi-step tasks, "like ones that run code, create files, or use your connected apps and browser, use more of your usage than a quick question."

By default the merged Claude asks before it takes an action. Users can switch it to keep working and check in only when something needs a closer look. On Team and Enterprise, an admin toggle already decides whether members may use Cowork's automatic-approval mode.

When should a business team use Cowork?

Cowork fits work that has three traits: it takes several steps, its inputs sit in files or connected apps, and the output is something a person reviews before it goes anywhere. A weekly pipeline summary, a month-end reconciliation of two exports, a first-pass review of a contract folder, a deck built from a report.

Two capabilities matter most for delegation. Cowork can schedule a task at any cadence and run it unattended, and it keeps going after you close your laptop when the session runs in the cloud. Both are also why Anthropic's safety guidance tells you not to "schedule tasks that access sensitive files, send messages on your behalf, make purchases, or take other actions that are difficult to undo." Start scheduled Cowork tasks on work where a wrong output costs you a re-run, not a customer email.

Cowork is the wrong tool when the task is really a piece of software: when you want the same logic to run the same way every time, be reviewed as code, and be fixed in one place when it breaks. That is where Claude Code comes in, even if nobody on the team calls themselves an engineer.

When is Claude Code the better choice, even outside engineering?

Choose Claude Code when the work depends on files you maintain over time: scripts, instructions, configuration. We run part of our own marketing operations this way. A scheduled Claude Code routine works from a folder of Python scripts and a written runbook, and three properties of Claude Code made it the right home for that job.

• Rules live in files. Claude Code reads permission rules from settings files, and a shared .claude/settings.json sits in the project where anyone can review it. Our routine only runs commands that match an allowlist exactly. When an early version chained several commands into one, the chained command matched nothing on the list and the run stalled waiting for approval. The fix was to run every script as its own command, which is now written into the runbook.
• Gates are scripts. A quality check runs before anything is published and exits with an error if the draft fails. The routine cannot talk its way past an exit code.
• Verification is part of the job. Each run ends by fetching the live page and checking the change is actually there, then writing one log line, including on runs that ship nothing.

Cowork could produce a similar draft. What Claude Code gave us is an operation we can read, diff and hand to someone else. If your team's recurring task has started to look like "run these five scripts in order and check the result," it has become a Claude Code job. Our guide to rolling out Claude Code across an engineering team covers the repository instructions, permission rules and review habits in detail.

Which one should you use? A decision flow

Most teams end up using at least two of the three. Operations, finance and sales staff work in chat and Cowork. Engineers, and whoever owns the scripted parts of your operations, use Claude Code. Standardising on one product for the whole company forces every task through a tool built for a different kind of work.

What should admins decide before turning Cowork or Claude Code on?

On Team and Enterprise plans, the two products are governed in different places.

For Cowork, Anthropic's Team and Enterprise admin article lists the controls:

• An organisation-wide toggle under Organization settings turns Cowork off for everyone.
• Cloud sessions are on by default for Team and off by default for Enterprise, where an admin grants them to a group through custom roles.
• Separate toggles decide whether members may use "Automatically approve" mode and "Always allow" for connector tools. The connector setting is off by default.
• Cowork sessions through Claude, Claude Desktop and Claude Mobile are captured in the Compliance API, and events can stream to your SIEM through OpenTelemetry.
• Local sessions store conversation history on the member's computer. Anthropic states this data "is not subject to Anthropic's standard data retention policies, and admins cannot centrally manage or delete it."

That last point decides a lot for regulated teams. If you need central deletion, favour cloud sessions, or keep sensitive folders out of Cowork until deletion endpoints for local sessions exist. Anthropic's safety guidance also recommends dedicated working folders over broad access to sensitive files.

For Claude Code, control sits in settings files that stack in a fixed order. Managed settings, deployed by your organisation through a managed-settings.json file, device management or the claude.ai console, sit at the top and override anything a developer sets locally. That is where company-wide permission rules belong.

On Enterprise, role-based access with fine-grained permissions decides which groups get which capabilities; Cowork's cloud sessions, for example, are granted to a group through custom roles. Our Claude Enterprise rollout guide covers identity, roles and spend limits in the order we set them up.

Does Cowork or Claude Code cost extra?

Neither is a separate purchase on paid plans. Prices below are from Anthropic's pricing page on 29 September 2026, before tax.

The seat price is the smaller question. Anthropic's help center says multi-step tasks use more of your usage than a quick question, and its Enterprise pricing notes that usage cost "scales with model and task." The people who delegate the most work hit limits first. On Team, that is the case for giving premium seats to heavy users and standard seats to everyone else. On Enterprise, where usage is billed at API rates on top of seats, it is the case for spend limits per group. Our Claude for business adoption page sets out how we plan a controlled pilot, access boundaries and the operating model before a wider rollout, and Claude Code for companies covers the engineering side.

Frequently asked questions

Is Claude Cowork the same as Claude Code?

No. They share the same agentic architecture, but Claude Code is built for codebases and runs in a terminal, IDE, the desktop Code tab or the web. Cowork is built for tasks across your files, connected apps and browser, with no terminal involved.

Can non-developers use Claude Code?

Yes, through the desktop app's Code tab or the web, without installing anything in a terminal. It makes sense when the task depends on scripts or instruction files you maintain. For one-off tasks on documents and apps, Cowork is the simpler fit.

Is Cowork available on the free plan?

No. Anthropic lists Cowork on paid plans only: Pro, Max, Team and Enterprise. Claude Code is also not included on Free.

Does Cowork run on my computer or in the cloud?

Either. Local sessions run the agent on your device and execute code inside an isolated virtual machine, with access limited to folders you connect. Cloud sessions, in beta, run in a temporary sandbox on Anthropic's infrastructure and keep going after you close your laptop.

What happened to Cowork in September 2026?

On 16 September 2026 Anthropic began merging Cowork and chat into a single Claude app, starting with Pro and Max. Existing Cowork chats, projects, connectors and skills carry over. Team and Free plans follow, and Enterprise admins get at least 30 days' notice.

Do we need both Cowork and Claude Code?

If you have an engineering team, you will likely use both, and the same Team and Enterprise seats include both. Decide which work goes where and who governs each.

How this article was produced

Written by the ATI implementation team. Product, plan and admin details were verified on Anthropic's pricing page, help center, product pages, blog and Claude Code documentation on 29 September 2026. The operating details about our own Claude Code routine come from ATI's internal runbook and logs. AI assistance was used in research and drafting; a human owns every claim and recommendation in it.