Claude Cowork: What It Is and How to Use It

What Cowork actually is

If you have only used Claude as a chat box — ask, get an answer, copy it out — Cowork is a different thing wearing the same brand. You do not have a conversation. You delegate a job.

The practical difference is who does the assembling. In a chat, you gather the inputs, paste them in, read the reply, and stitch the result together yourself. In Cowork you describe the outcome, and it does the gathering, the steps and the stitching. You come back to something finished.

Cowork vs Claude Code vs the chat box

This is the comparison people search for most, and the confusion is understandable — all three are Claude, and the names do not tell you who each is for.

The short version: chat is for thinking, Cowork is for delegating, Claude Code is for building. Most non-technical teams will get the most from Cowork and never need to open Claude Code — though the boundary is softer than it used to be, and plenty of non-developers now use Code to build small internal tools.

Is it free, and where does it run?

Cowork is part of Claude's paid plans rather than something you buy separately, and there is no free-standing free tier for it — the free Claude account gets the chat experience. Which paid plans include it, and at what usage limits, has been moving as Anthropic expands the rollout, so check the current plan comparison rather than trusting any article on that specific point, including this one.

Where it runs is simpler and more useful to know: the work happens on Anthropic's servers, and you reach it from the web, the desktop app on Mac or Windows, or your phone. Because the session belongs to your account rather than to a machine, you can start something at your desk, check it from your phone in a meeting, nudge it — “actually, leave out the Q3 numbers” — and collect the result from whatever device you happen to have later.

How to use it: your first three tasks

The mistake almost everyone makes is starting with something ambitious and important. Start instead with something recurring and low-stakes, so that when it gets something wrong — and the first attempt usually does — nothing breaks and you learn how to brief it better.

• Something you do every week that you resent. Compiling a report from the same four places. Summarising a recurring meeting. Formatting the same kind of document. Recurring is what matters — you want to run it more than once so you can improve the brief.
• Something with a pile of inputs and a clear output. Forty emails into five themes. A folder of documents into one summary. This is where it comfortably beats doing it yourself, and where the result is obviously right or obviously wrong.
• Something scheduled, once the first two work. A Monday briefing built from last week's threads and this week's calendar, sitting ready before you open your laptop. This is the one that changes how the week feels.

Brief it the way you would brief a capable new colleague who has never seen your company: what the output should look like, what good means, what to leave out, and what to do if something is ambiguous. The instinct to write a short prompt is worth resisting here. A task you describe in three sentences comes back needing three rounds of correction.

Why “you can walk away” is the whole point

Think about what makes delegating to a person valuable. It is not only that they are competent. It is that once you have handed something over, you get your attention back. You do not stand over their shoulder for an hour.

AI that runs on your own device never quite had that property. Technically you could start something and look away, but you were tethered — you could not close the laptop or go into a meeting without risking the work stopping. So most people babysat it, which is exhausting and quietly caps how much anyone is willing to hand over.

Cutting that tether is the actual upgrade. Once walking away is genuinely safe, the tasks people are willing to delegate get bigger, because the cost of delegating — sitting there watching — drops to nothing.

What it is and isn't suited to

Being honest about the second half of this saves teams a lot of disappointment.

It suits work that is multi-step, involves gathering from several places, has a recognisable finished shape, and recurs often enough that improving the brief pays off. The low-glamour work that eats mornings.

It does not suit anything where you cannot describe what good looks like before it starts, anything requiring judgement that depends on context nobody has written down, or anything where being wrong is expensive and nobody will check the output. That last one is worth saying plainly: the failure mode is not that it refuses, it is that it produces something confident and wrong and nobody notices because it looked finished.

Review the first several runs of any task properly. Once you have seen it handle the same job right a few times, you can relax — and by then you will have a real sense of where its judgement is reliable and where it is not.

Working out which of your team's recurring tasks are worth handing over — and writing briefs good enough that the output comes back usable — is most of what a Deployed Kickstart half-day covers. The Partner programme is where teams go from one working task to a dozen.

Frequently asked questions