Claude Code vs Cowork: which one to use for what
Claude Code vs Claude Cowork: Cowork is now part of the Claude app for documents, research, and files; Claude Code is for software. When to use each.
A PM asks whether to install Claude Code to write PRDs, because "it's the agent one." An engineer wonders if Cowork could run their test suite. Both are asking the right question about the wrong tool. Anthropic has two agents for two kinds of work, and the line between them recently moved.
This guide compares them from Anthropic's Cowork product page, its announcement that Cowork is now part of Claude, and the Claude Code docs, checked on 16 November 2026.
The short answer
| Claude Code | Claude (with Cowork) | |
|---|---|---|
| Built for | Software development | Knowledge work |
| Works in | A code repository | Folders, documents, and connected tools you choose |
| Typical output | Code changes, tests, pull requests | Documents, decks, spreadsheets, research |
| Where | Terminal, IDE, desktop Code tab, web, mobile | Claude app on web, desktop, and mobile |
| Runs while you're away | Cloud sessions, scheduled tasks | Yes, including scheduled tasks |
| Configured by | CLAUDE.md, skills, hooks, settings, MCP | Projects, connectors, skills |
What changed with Cowork
Cowork launched as a separate place in the Claude app for bigger, agentic work. On 16 September 2026 Anthropic announced that Cowork and chat were merging into one Claude: you ask for what you need, and Claude brings in Cowork's abilities when a task calls for working with files. The rollout started with Pro, Max, and Ultra, reached Enterprise on 23 October, and Team on 12 November.
Anthropic's reason: people found it frustrating to decide where a task belonged, and work started in one place didn't carry to the other. Existing Cowork chats, projects, artifacts, connectors, and skills stayed where they were.
Claude Code didn't merge. It's still the separate tool for software.
What Cowork does
From Anthropic's product page:
- Works across your files and tools: in folders and tools you choose, delivering finished work for review rather than chat replies to copy.
- Browses for you: a built-in browser in the side panel, separate from your own logins and tabs.
- Keeps going: close the laptop and the task continues; schedule tasks to run unattended.
- Splits big projects: parts run in parallel, such as research and drafting.
- Shows its steps: the files it opens, the tools it uses, and the choices it makes, so you can redirect it.
Typical jobs: a weekly metrics deck built from analytics and Drive, reconciling spreadsheets, first-pass contract review, analyzing a quarter of sales call notes.
What Claude Code does
Claude Code works inside a code repository. It reads the codebase, edits files, runs tests and commands, uses git, and opens pull requests. It's configured per repository through CLAUDE.md, skills, hooks, permission rules, and MCP servers, so a team's setup is versioned with the code. See Claude Code best practices.
Which to use
| Task | Use |
|---|---|
| Fix a bug, add a feature, refactor | Claude Code |
| Review a pull request | Claude Code |
| Prototype a UI to test an idea | Claude Code, or Claude for a quick mock |
| Write a PRD or one-pager | Claude |
| Synthesize 30 customer interviews | Claude |
| Build the weekly metrics deck | Claude, scheduled |
| Write a spec next to the code it changes | Claude Code |
| Understand how a feature actually works today | Claude Code, reading the code |
For product managers, Claude covers most of the job. Claude Code becomes useful when the question is about the code itself. See how to use AI agents as a product manager.
Skills across both
Both use skills in the Agent Skills format. Claude Code's docs say skills enabled for your claude.ai account load in Cowork sessions, cloud sessions, and terminal sessions signed in with that account. Skills that exist only in ~/.claude/skills/ on your machine don't reach Cowork. In a Cowork session, shell command lines in a skill are replaced with a placeholder rather than run.
The handoff between them
The PM writes the PRD in Claude. The engineer builds it in Claude Code. In between, decisions get made: in the PRD review, in Slack, in a comment on a pull request. Neither agent sees the other's conversations, so a scope change agreed in a Claude chat doesn't reach the Claude Code session building the feature unless someone carries it over.
Where Lockstep fits
Lockstep carries those decisions across. It captures them from PRDs, Slack, and pull requests, routes each to its owner for approval, and briefs Claude Code sessions on the approved decisions that apply to the work. Session briefings are a Claude Code feature; other MCP clients can query the decisions through Lockstep's tools.
See Lockstep for product teams.
Sources checked 16 November 2026
- https://claude.com/product/cowork
- https://claude.com/resources/articles/cowork-is-now-claude
- https://code.claude.com/docs/en/skills
- https://code.claude.com/docs/en/desktop
Related reading
For Claude Code's own front ends, see Claude Code desktop vs CLI vs VS Code. For prototyping versus shipping, see vibe coding vs agentic coding. For Claude Code versus the Claude app in general, see Claude Code vs Claude.
Frequently asked questions
- What is the difference between Claude Code and Cowork?
- Claude Code is built for software development: it works inside a code repository, reads and edits code, runs tests and commands, and opens pull requests. Cowork handles knowledge work: it works across folders and tools you choose, builds documents, decks, and spreadsheets, browses the web, and runs scheduled tasks.
- Is Claude Cowork still a separate product?
- Not for most users. Anthropic announced on 16 September 2026 that Cowork and chat are merging into one Claude, rolling out to Pro, Max, and Ultra first, then generally available for Enterprise on 23 October and Team on 12 November. Claude brings in Cowork's capabilities when a task needs them.
- Should a product manager use Claude Code or Cowork?
- Mostly Claude, with its Cowork capabilities, for PRDs, research synthesis, decks, and recurring reports. Use Claude Code when the work touches the codebase: prototyping, reading how a feature actually works, or writing a spec next to the code it describes.
- Do Claude Code skills work in Cowork?
- Skills enabled for your claude.ai account load in Cowork sessions, cloud sessions, and terminal sessions signed in with that account. Skills only in ~/.claude/skills on your machine don't reach Cowork. Anthropic's docs say shell command lines in a skill don't run in Cowork sessions.
- Can Cowork run tasks when my laptop is closed?
- Yes. Anthropic's product page says Cowork keeps going when you close your laptop and can run scheduled tasks unattended. Claude Code has the same through cloud sessions and scheduled tasks.
Keep reading