For executives and owner-operators trying to figure out where their work should live.
Three surfaces, one underlying model. The differences are not about intelligence — they're about surface, context, and what kind of building is actually possible.
A conversation with Claude on web, desktop, or mobile. You ask, Claude responds. Can create single files (Excel, PowerPoint, Word, PDF) when you enable file creation in settings. Best for thinking, drafting, and one-off deliverables. Works anywhere.
A desktop workspace where Claude reads, edits, and creates files in folders on your computer. Projects tie to local folders with their own instructions and memory. Runs multi-step tasks autonomously across many files. Mobile via Dispatch.
A terminal-based agent built for developers. Not relevant to this guide. The real decision for executives lives between Chat and Cowork — that's where this guide focuses.
The rest of this guide explains the tradeoffs. But if you'd rather skip ahead and decide where your first project should live, we can do that instead.
Help me decideBoth Chat and Cowork run on the same Claude. Both can think. Both can create files. The model is the same. The differences are about surface, context, and what kind of building is actually possible.
| Chat | Cowork | |
|---|---|---|
| Where it runs | Web, desktop, mobile | Desktop only (Mac or Windows), mobile via Dispatch |
| File access | Only what you upload in the conversation | Full access to folders you grant on your computer |
| File creation | One file at a time. Max 30MB. | Same file types plus multi-file projects, codebases, websites, structured outputs |
| Multi-file output | Not supported. Single-file artifacts only. | Native — folders of files, code projects, multi-component deliverables |
| Memory | Inside Chat Projects only | Inside Cowork Projects only — does not sync with Chat Projects |
| Multi-file input | Limited by upload size and effort | Native — point it at a folder of 200 files and walk away |
| Autonomous execution | No — turn by turn | Yes — multi-step tasks while you do other things |
| Mobile | Native | Through Dispatch (paired to desktop) |
| Setup overhead | None | Real — folder, Project, and instructions per stream of work |
| Usage limits | Standard | Burns through limits faster |
| Best for | Thinking, single deliverables, anywhere work | Multi-file synthesis, ongoing project workspaces, file-based work |
Chat creates files, but it has hard limits on what kind of building is possible. The moment the work needs more than one file or needs to live on your machine, the wall is right there.
No setup. Works on every device. Great for thinking on the move, quick questions, and single-file deliverables. The cost is that nothing persists beyond the conversation unless you do something with it. Context doesn't compound. And the moment you need real multi-file building, you're stuck.
It requires setup — folders, Projects, instructions — and a desktop that stays awake. The payoff is that every conversation inside a Project builds on the last one, and Claude can actually build real projects with structure, not just single artifacts. You can hand off multi-step tasks across many files and walk away.
A Chat Project and a Cowork Project are different objects with different memory. You can't natively move a conversation from one to the other. If you start something in Chat and want to continue it in Cowork, you have to bridge it manually — usually by summarizing and dropping the summary into the Project folder.
Given that both surfaces can think, but only Cowork can fully build, the question for any executive is:
That question has two valid answers. Each one points to a different workflow. Both are valid. Pick the one that matches how your brain actually operates, then commit to it.
Verbal processors and free-thinkers tend toward A. Builders and systems-thinkers tend toward B. Neither is more sophisticated than the other.
You use Chat as your daily thinking partner. Lightweight, mobile-friendly, anywhere. When a conversation produces something worth executing, you summarize it and move it into the relevant Cowork Project to build.
You set up Cowork Projects for your real streams of work and do everything inside them — thinking, sparring, drafting, building. No handoff. No transfer. The Project accumulates context the longer you use it.
Workflow A lives or dies on one habit. You must summarize Chat conversations into a brief before you move on — otherwise you'll have three days of thinking spread across five conversations and a wall of context you don't want to retype.
The closing prompt to make this automatic:
Run it at the end of any Chat conversation that touches real work. Save the summary. Drop it into the Project folder. Now Cowork has the context to build from without you re-explaining anything.
If I have a great conversation in Chat about a client strategy or a positioning question, the odds I'll close it cleanly with a brief and move it into the right Project are maybe 50/50. The other half of the time, that thinking is gone — buried in a thread I'll never find again, disconnected from the work it was supposed to inform.
Cowork removes the question. I'm already in the Project. The thinking is already in context. When the conversation produces something worth building, I build it right there. No summary. No transfer. No leakage.
I also don't really separate thinking from building in my own head. When I'm thinking through a client problem, I'm already half-drafting the solution. Splitting that across two surfaces would mean breaking my flow twice — once to summarize, once to switch.
"Think freely first" → Workflow A. Use Chat as your thinking layer. Build the summary habit.
"Land in the right place from the start" → Workflow B. Set up Projects. Live in Cowork.
Pick a workflow and run it for at least a month before you evaluate.
Both workflows require Cowork Projects to exist. The difference is how often you start work outside of them. The setup is the same.
If you're running Workflow A, your Projects are the workshop you bring finished thinking into. If you're running Workflow B, your Projects are your operating system.
Mobile Chat is fine for thinking on the go. Use the summary prompt before you put the phone away. When you're ready to build, Dispatch the brief to the right Project from the same mobile app.
Anything related to active work goes through Dispatch, always. Name the Project in the first line of every dispatched task:
Dispatch doesn't have a Project selector in the mobile UI yet. You route by naming the Project. Make this reflex.