For executives and owner-operators trying to figure out where their work should live. Pick a workflow, run it for a month.
Three surfaces, one underlying model. The difference isn't intelligence — it's 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. 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. 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.
The rest of this guide explains the tradeoffs. If you'd rather skip ahead and decide where your first project should live, we can do that instead.
Help me decide →Both run on the same Claude. Both can think. Both can create files. The differences are about surface, context, and what kind of building is 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 types plus multi-file projects, sites, structured outputs |
| Multi-file output | Not supported. Single artifacts only. | Native — folders of files, multi-component deliverables |
| Memory | Inside Chat Projects only | Inside Cowork Projects only — does not sync with Chat |
| 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 |
| Usage limits | Standard | Burns through limits faster |
| Best for | Thinking, single deliverables, anywhere work | Multi-file synthesis, ongoing project workspaces |
No setup. Works on every device. Great for thinking on the move, quick questions, and single-file deliverables. The cost: nothing persists beyond the conversation, 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: every conversation inside a Project builds on the last, and Claude can build real projects with structure, not just single artifacts.
A Chat Project and a Cowork Project are different objects with different memory. To move something from one to the other you bridge it manually — usually by summarizing and dropping the summary into the Project folder.
That question has two valid answers. Each points to a different workflow. 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.
You use Chat as your daily thinking partner. 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. The Project accumulates context the longer you use it.
Workflow A lives or dies on one habit: summarize a Chat conversation into a brief before you move on — otherwise you'll have three days of thinking spread across five conversations. The closing prompt that makes it automatic:
"Summarize this conversation as a brief I can drop into my [Project name] Cowork Project. Include the question, key decisions, reasoning, and recommended next steps."
Run it at the end of any Chat conversation that touches real work. Save the summary, drop it into the Project folder, and Cowork has the context to build from without you re-explaining anything.
If I have a great Chat conversation about a client strategy, 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.
Cowork removes the question. I'm already in the Project, the thinking is already in context, and when the conversation produces something worth building, I build it right there. No summary, no transfer, no leakage.
"When I have an idea related to active work, do I want to think freely first and decide later if it's worth keeping — or do I want everything to land in the right place from the start?"
"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.
Use a synced location (iCloud Drive, Dropbox, OneDrive, or Google Drive Desktop) so you can access outputs from any device.
Existing docs, notes, references — anything Claude should know going in.
Name the Project the same as the folder. (See the next section on when to attach the folder.)
Your role, context, standards, voice, what "good" looks like. The highest-leverage move, and the one most people skip.
So mobile tasks route to the right desktop Project.
Reflects the desktop app as of July 2026; re-verify if you're reading this later.
One detail decides whether a Project is reachable from your phone and the web — and it comes down to when you attach the folder.
Create the Project without attaching a folder and it lives in the cloud — visible and usable on web and mobile. Attach a folder to the Project itself and it ties to one computer, so the web and phone versions can't fully reach it. But Cowork needs a folder to read and write real files — so you attach the folder at the Cowork session, not on the Project.
Now it's visible on web and mobile.
The workspace everyone points to. Keep new work in project subfolders, not the root.
Cowork reads and writes there. Everyone points their Cowork sessions at the same folder.
Mobile Chat is fine for thinking on the go. Use the summary prompt before you put the phone away, then Dispatch the brief to the right Project from the same app.
Anything related to active work goes through Dispatch, always. Name the Project in the first line of every dispatched task:
"In the Acme Acquisition project: pull the latest financials from the folder, compare against the term sheet draft, and flag inconsistencies in a memo I can review tonight."
Dispatch routes by the Project you name. Make it reflex.
Real, recurring work areas — not aspirational categories.
iCloud Drive, Dropbox, OneDrive, or Google Drive Desktop.
The instructions are the highest-leverage move. Don't skip.
So mobile thinking has somewhere to land.
Don't admire the setup. Use it.
After that, the habit takes over.