Claude's Chat, Cowork, and Code — Which One and When

Where the three live and which plans open them

There are three surfaces for Claude: the web at claude.ai, the mobile app, and the desktop app. All three products exist across all three surfaces, but what you see depends on your plan.

Chat is available on every plan including free. Cowork and Code require a paid plan. On desktop they open at Pro and up; on mobile and web they landed first for Max and up. A rollout to Pro was said to be coming, so depending on when you read this they may already be there.

The order of judgment matters. First decide whether the work is a conversation, a delegation, or a build. Only then check whether that opens on your plan and device. Reverse the order and you end up picking from what happens to be available — which usually means staying in Chat.

Chat is an intern — it is done when it answers

Chat is the one everyone knows, and it behaves the same across all three surfaces. Brainstorming, writing, research, working an idea into shape. It is a thinking partner.

You can extend it. Projects give it permanent context about your work, connectors let it use your other tools like email or calendar, and artifacts open a small app or document window beside the chat. At its core it is still a conversation.

The point is where it stops. Everything Chat does — even when it makes a file or builds a small dashboard — happens inside one turn. Then it hands it back and waits for you. That is asking an intern. You get back what you asked for, and making that answer usable stays your job.

That is not a flaw. Often the work is the conversation: brainstorming names or angles for a new product, weighing a pricing change, understanding a contract clause you do not fully follow.

Cowork is a team lead — it does not stop until the goal is met

Cowork is where you stop asking Claude questions and start assigning it work. Give it a goal and it goes off to complete it. It builds its own checklist, works through it step by step, and keeps going for however long it takes. It often splits into sub-tasks running in parallel, then returns with a finished result.

The obvious objection: with a thorough prompt, Chat already handles complex tasks, connects to tools, and creates files. So what actually differs? Three things.

First, the finish line. Chat is done the moment it gives you an answer, whether or not the job is actually finished. Cowork does not stop until the goal is achieved, and that might take two minutes or forty. Chat works to produce a response; Cowork works to complete a task. It is a vending machine versus a kitchen. The vending machine takes a prompt and returns a result. The kitchen takes an order, gathers ingredients, works a multi-step recipe, plates it, and brings it out finished.

Second, it gets its own workspace. On desktop that is your computer; on mobile or web it is a fresh cloud sandbox. Either way it gets an environment it can keep building on for the whole job — a desk it gets to keep. Chat grabs a calculator once and puts it away. Cowork leaves everything on the desk: it spreads out research, saves drafts, changes approach when a different one looks better, and builds up across the session.

Third, it can run without you, through scheduled tasks. Set it up once, choose a schedule, and it runs on its own. Monday morning, while you are still asleep, Cowork is reading last week's email threads, pulling meeting transcripts, checking recent news on your client. By the time you sit down with coffee there is a briefing doc waiting and a follow-up email already drafted. You prompted nothing that morning. You set it up once, months ago.

Desktop versus cloud — what actually changes

Cowork comes in two versions: desktop, running on your computer, and mobile/web, running in the cloud. The same system underneath; only where it runs differs.

It matters for one reason: whether you want to work on local files. The desktop version takes a folder on your actual computer, sees everything in it, opens files, edits them, creates new ones, and will reorganize an entire messy folder for you.

Mobile and web Cowork runs in the cloud instead. The upside is real: it runs without your computer being open. Out at dinner and you remember a quarterly report is due — fire it off from your phone and review it when you get home. You can have it notify you when it finishes or when it hits a decision only you can make. Scheduled tasks work the same way: no device needs to be online. Your computer can be closed and your phone off, and it keeps going.

What it cannot do is touch your local files. To be precise, a mobile or web session can reach them, but only while the desktop app is open on that computer. That means connecting it in advance and leaving the machine on before you go out. Possible, but most people are better off treating local file access as a desktop-app thing.

The video's presenter uses a simple workaround: put any files Cowork should work with in a Google Drive folder and use that as its home base. With the Drive connector set up, Cowork reads from that folder and saves its finished work there — so it no longer matters whether your computer is on, and any surface reaches the same files.

Code is Einstein — it makes what did not exist

If Cowork is your assistant, Claude Code is your engineer. Apps, websites, automations, Chrome extensions, productivity tools — it writes the actual code for whatever you describe.

You do not have to be a developer. Describe what you want in plain English and it writes the code to make it exist. With recent models, what you can build through prompting alone is considerable.

Code is on all three surfaces too, but like Cowork it works differently across them. On desktop you assign it a folder and it builds the entire project there — all the files, all the code, everything it needs. Same as Cowork, except it also builds its own codebase in that spot rather than only working with your files.

You will see people run it in a terminal or inside developer tools, but none of that is required. The desktop app is enough, and it is the better starting point if you are not technical.

Two paths for Code on mobile and web

The first is remote control. If Code is running on your computer at home, you can steer that exact session from your phone — check progress, answer its questions, redirect it. The work still happens on your computer; the phone is a window into it. So the machine has to be on, and you have to enable the remote session from that computer first.

The second is cloud sessions, which need a GitHub repository. A repo is just a project folder that lives online instead of on your computer. If you do not have one, create a free GitHub account and make an empty repository. Or start something on desktop, ask Code to push it to GitHub, then connect the cloud session to that repo.

If that sounds like the Cowork section, it should. Cowork and Code are the same agentic architecture underneath — the same core that plans, works, and keeps going without you. Only what gets loaded changes. Your files and connected apps and it is Cowork; add a code repository and it is Code.

The signal that you are in the wrong mode

Diagnosis is easier than it sounds. It is the moment you start taking Chat's output and assembling it into something — copying it into docs, stitching pieces together, doing busy work around the answer.

Instead of using your thinking partner, that work should have been delegated. An hour spent in Chat may have been an hour of work Cowork could have finished while you slept.

There is a signal in the other direction too. If the answer to your problem is 'I wish this existed,' that is Code's job — a tool that scrapes and formats data from a site you check regularly, an internal dashboard pulling scattered numbers into one view, the mobile app for the idea you have been sitting on.

The decision on one page

Chat to think, Cowork to delegate, Code to build. Once the difference is clear you stop defaulting to Chat for everything and doing the assembly yourself. Catch yourself copy-pasting into a doc and that is a Cowork job; catch yourself wishing a tool existed and that is a Code job.