Claude has two features with almost the same name: Chat Projects and Cowork Projects. Same name, same model, nearly identical interface. But under the hood, they're fundamentally different — and that's exactly what confuses people and costs them both time and money.
I've seen the pattern again and again: Someone uses a Chat Project for a task that requires Cowork, gets frustrated that Claude "forgets" and "doesn't deliver" — and draws the wrong conclusion that the tool doesn't work. Others do the opposite: use Cowork for a simple brainstorm and burn through their monthly quota on nothing.
What you get from this guide
A clear mental model of when to use what. Concrete setup recipes. Seven insider tips per tool. Fourteen real-world use cases. And a collection of system prompts you can copy-paste and start using immediately.
> In a hurry? Read chapter 2 (the 60-second version) and chapter 7 (the decision guide). That covers 80%. Come back to the rest when you actually get started.
> An honest warning about costs: Cowork is expensive. A single Cowork session can easily cost the same as 15–25 normal chats, because Claude calls tools, reads files, verifies output, and writes back. That doesn't mean Cowork is bad — it means you should use it for tasks where the output justifies the cost, and Chat Projects for the rest.
The two projects in 60 seconds
Chat Projects are a folder with context
You upload files (up to 20 documents), write an instruction, and chat with Claude. Claude reads your files, answers your questions, and you copy-paste results out of the chat. Great for analysis, brainstorming, and writing help. Lives in the browser at claude.ai.
Cowork Projects are a workspace
You give Claude access to a folder on your computer. Claude reads your files, writes new ones, updates existing ones, and can connect to Slack, Gmail, Notion, and Canva via plugins. It's closer to delegating to a colleague than asking questions. Requires the Claude Desktop app and a Pro plan or higher.
The core difference
Chat reads what you upload. Cowork reads and writes directly in the files on your computer. It sounds like a small difference. It's not.
> The metaphor that made it click for me: Chat Projects: You send one document at a time to a colleague who responds from another office and isn't allowed to save anything. Cowork: The same colleague sits at the desk next to you with access to the entire drawer, your emails, and Slack. Both are useful — just not for the same thing.
Before you start
| Requirement | What and why | Where |
|---|---|---|
| Claude account | Chat works on all plans. Cowork requires Pro or higher. | claude.ai |
| Claude Desktop | Only needed for Cowork. The browser can't read local files. | claude.com/download |
| A folder with files | For Cowork: your documents, data, or projects. | Your computer |
| A concrete goal | The most important requirement — and the one people forget. | Your head |
Chat Projects — Setup and 7 insider tips
Setup in 5 steps
1. Open claude.ai and log in
2. Create a new project with a descriptive name
3. Upload your files (keep it under 10 in practice)
4. Write a system instruction (spend 5 extra minutes)
5. Start a chat in the project
7 insider tips
1. Write the instruction like a job description — include role, tone, format, constraints, and an example
2. Use meta-prompting — ask Claude to write the instruction for you, then adjust
3. Keep the number of files under 10 — quality over quantity
4. Start each chat with context — chats share files, but not conversation history
5. Use Artifacts for structured output — ask explicitly for it
6. Search through previous chats — faster than scrolling
7. One instruction per project — not one for everything
Cowork Projects — Setup and 9 insider tips
Setup in 6 steps
1. Download Claude Desktop (claude.com/download)
2. Create a project folder on your computer
3. Put your starting material in the folder
4. Connect the folder in Claude Desktop
5. Install the skills you need
6. Start a session with a concrete goal
9 insider tips
1. Create CONTEXT.md as the very first thing — your onboarding of a new employee
2. Ask Claude to create DECISIONS.md — log all important choices with date and reasoning
3. Skills are recipes — tone, examples, do's and don'ts, and formatting rules
4. Connect external tools via plugins — start with one at a time
5. Define precisely what you want done — open tasks = high consumption
6. Use Git or backup — Claude writes directly in your files
7. Let Claude update its own instructions — the system gets smarter over time
8. Timebox your sessions — keeps focus and consumption under control
9. Always end with a status line — your onboarding for yourself tomorrow
Side-by-side comparison
| Feature | Chat Projects | Cowork Projects |
|---|---|---|
| Setup time | 5 minutes | 15 min + skills |
| Where it lives | claude.ai (browser) | Claude Desktop app |
| Plan requirement | All plans (Free, Pro, Max) | Pro or higher |
| File access | Upload manually each time | Direct access to folder on your computer |
| File production | Copy-paste from chat | Saved directly as Word, PPTX, HTML, PDF |
| Memory | Only within the same chat | Persistent via CONTEXT/DECISIONS.md |
| Integrations | None | Slack, Gmail, Notion, Canva, Drive, Linear |
| Skills/plugins | Not relevant | Yes — crucial for quality |
| Consumption per session | ~ same as a normal chat | 5–25× a normal chat |
| Best for | Analysis, brainstorm, one-off answers | Production, repetition, multi-file output |
Decision guide — 5 questions
| Question | YES → | NO → |
|---|---|---|
| Do I need to produce new files that others will use? | Cowork | Chat |
| Will I do the same thing repeatedly with new input? | Cowork | Chat |
| Does Claude need to remember what we decided last time? | Cowork | Chat |
| Do I have at least a Pro plan? | Cowork possible | Chat |
| Do I need Slack, Gmail, Notion, or other integrations? | Cowork | Chat |
> Rule of thumb: If you answered yes to 3 or more — use Cowork. Otherwise start with Chat.
14 real-world use cases
Chat Projects — 7 use cases
1. Contract analysis — upload contracts, find risks and ambiguities
2. Brainstorm partner — idea generation without saving anything
3. Meeting preparation — briefing based on agenda and background documents
4. Code review and feedback — find bugs and security issues
5. Language proofreading and tone — spelling, word choice, and tone
6. Research assistant — ask questions across 5–10 sources
7. Pitch training — feedback and skeptical investor role-play
Cowork Projects — 7 use cases
1. Weekly status report — Word report generated every Monday
2. Presentation production — PowerPoint from notes and data
3. LinkedIn content machine — posts in your voice directly to file
4. Client onboarding package — welcome email, guide, video script, and checklist
5. Data analysis and visualization — charts and insights report from Excel
6. Website prototype in HTML — landing page from a brief
7. Multi-channel marketing — one message, seven outputs in different formats
The 6 biggest mistakes
1. Bad system instructions — spend 5 extra minutes: role, tone, format, constraints, example
2. Chat for repetitive work — move to Cowork, set it up once
3. Cowork without DECISIONS.md — create it on day 1
4. Vague Cowork tasks — precision controls the budget
5. No backup of Cowork folder — use Git or duplicate daily
6. Using Cowork for brainstorming — brainstorming belongs in Chat
🎓 Want hands-on training? Book our Copilot Workshop or Copilot Agent Workshop.
📬 Subscribe to the "AI, Built Human" newsletter on Substack — weekly insights on AI in practice.
Stefano Vincenti · AI Advisor & Trainer · aitrainer.dk · External Lecturer, IT University of Copenhagen · Cofounder & CTO BotTellMe · Partner, TryZone