Claude: Chat vs Cowork vs Code
Same AI. Three products. Here's how to pick the right one.
Chat Cowork Code
| Chat | Cowork | Code | |
|---|---|---|---|
| What it is | You type, Claude answers. A conversational AI chatbot. | Claude sits on your desktop. It reads your files, creates new ones, and works autonomously. | A CLI agent in your terminal. It reads your codebase, writes code, and runs commands. |
| Who it's for | Everyone — students, professionals, curious minds. | Knowledge workers — marketers, analysts, PMs, writers. | Developers, engineers, and technical builders. |
| Access | Browser, phone, or desktop app. | Desktop app only (macOS & Windows). | Terminal CLI, VS Code, JetBrains, GitHub, Slack. |
| Setup | Zero. Open and start typing. | ~10 min. Download app, pick a folder, add your files. | ~5 min. Install via npm/brew, authenticate, configure CLAUDE.md. |
| Runs in | Cloud (Anthropic servers). | Sandboxed VM on your computer (safe & isolated). | Directly on your local machine (full system access). |
The Real Difference
Chat
The skill you need
Clear prompts
Output quality
Generic unless you prompt very well
The vibe
Texting a very smart stranger
Superpower
Instant answers, brainstorming, web search, quick analysis
Cowork
The skill you need
Clear context files (your style, your rules, your examples)
Output quality
Sounds like you, because it reads your files
The vibe
Working with an assistant who read every brief
Superpower
Creates real deliverables — docs, slides, spreadsheets — in your folders
Code
The skill you need
A codebase and clear architecture decisions (CLAUDE.md)
Output quality
Production-ready, because it understands your whole repo
The vibe
A senior dev pair-programming with you in the terminal
Superpower
Multi-file edits, git workflows, running tests, shipping PRs
Feature Comparison
| Chat | Cowork | Code | |
|---|---|---|---|
| Answer questions | Yes | Yes | Yes |
| Create real files (Excel, Word, PDF) | Save / download | Yes — directly in your folders | Yes — in your repo / filesystem |
| Read & write local files | No | Yes (sandboxed folder) | Yes (full filesystem) |
| Run terminal commands | No | In sandboxed VM | Yes — full access |
| Use plugins / skills | No | Yes — install from library | Yes — slash commands, hooks |
| MCP connections (Slack, Drive, etc.) | Limited (via Integrations) | Yes | Yes — fully configurable |
| Git & GitHub integration | No | No | Yes — commits, PRs, reviews |
| Scheduled / automated tasks | No | Yes | Yes — CI/CD, cron-style |
| Computer use (click & navigate) | No | Yes | Yes |
| Extended Thinking | Manual toggle | On by default | On by default |
| Search the internet | Yes | Yes | Yes |
| Projects support | Yes — web & desktop | Yes — with file & memory persistence | Via CLAUDE.md & repo context |
Projects Work Across All Three — But Differently
Projects let you organize context, files, and instructions into reusable workspaces. But they manifest differently in each product:
Chat Projects
Upload files and set instructions. Every new chat in that project inherits the context. Great for recurring topics.
Cowork Projects
Persistent workspaces with files, links, instructions, and memory. Context carries across sessions. Ideal for long-running work.
Code "Projects"
Your repo IS the project. CLAUDE.md files set coding standards, architecture decisions, and review checklists. Context is your codebase.
Context & Identity
| Chat | Cowork | Code | |
|---|---|---|---|
| Your identity | No. Every chat starts blank. | Yes, if you put info in text files inside your folder. | Yes, from CLAUDE.md and repo context. |
| Context input | You copy-paste into the chat. Every. Single. Time. | Write .md or .txt files once. Drop them in a folder. Point Claude to it. | Your codebase IS the context. Claude reads everything. |
| Memory | No. Gone when you start a new chat. | Yes, as long as you're in the same folder / project. | Yes, via session history and CLAUDE.md files. |
| Customization | System prompt in Projects, or per-message instructions. | Global instructions, plugins, skills, and MCP connectors. | CLAUDE.md, hooks, slash commands, MCP servers, .claude config. |
When to Use Each
Start with Chat if…
- •You have a quick question
- •You want to brainstorm or explore ideas
- •You don't need it to know your style
- •You want an answer, fast
- •You're on mobile or web
- •You need to search the web for info
Use Cowork when…
- •You're doing real work (reports, spreadsheets, slides)
- •You want Claude to create actual files
- •You want it to sound like you, not AI
- •You need long, deep sessions that don't break
- •You want tasks to run on a schedule
- •You need it to use apps on your computer
Use Code when…
- •You're building or maintaining software
- •You need multi-file code edits across a repo
- •You want automated PR reviews and git workflows
- •You need CI/CD automation or log analysis
- •You want maximum control and extensibility
- •You live in the terminal or your IDE
Quick tasks → ChatDeep work → CoworkBuilding software → Code
Chat has a free tier. Cowork and Code both require a paid plan (Pro $20/mo, Max $100–200/mo, Team $30/user/mo, or Enterprise). Cowork is desktop-only. Code is available everywhere developers work — terminal, IDE, GitHub, and Slack. Extended Thinking works in all three — always turn it on.
Want to master Claude Cowork? Our course covers everything hands-on.
View Course PricingResearch compiled March 2026 · Sources: claude.ai, support.anthropic.com, docs.anthropic.com