Claude Cowork: what it is, when to use it (and when not to)

7 min read  ·  Cowork primer  ·  Last updated 13 May 2026

Part of Learn Claude Code: The Complete Operator's Guide. For the operator's overview of Skills, Connectors, Cowork, and Artifacts, start there.

You have been using Claude as a chat tool. You type something. Claude replies. Conversation back and forth.

Cowork is different. You hand Claude a task. You walk away. You come back to a finished deliverable.

This is the plain-English explainer. What it is. When to use it. When to stay in chat. The first task you should run.

What Cowork actually is

Cowork is a separate mode inside Claude Desktop. You can find it as the "Cowork" tab at the top of the app.

Anthropic's own positioning is direct: "Cowork handles tasks autonomously. Give it a goal and Claude works on your computer, local files, and applications to return a finished deliverable."

In chat mode, you steer every step. Claude responds, you respond, repeat.

In Cowork mode, you describe the end state, hand over the task, and Claude executes the whole thing on its own. Multiple steps. Multiple tool calls. Files created, sorted, summarised. Tasks scheduled to run on Mondays.

It is the same Claude. Different working agreement.

The four jobs Cowork is built for

Anthropic specifically pitches Cowork as "the same capability [as Claude Code] with a simplified experience, designed for where non-technical knowledge work happens." They flag four use cases in particular, and operators we train at our Claude Code workshop end up using all four within their first month.

Notice what is common to all four: they involve your files. Chat works on words. Cowork works on files. That is the line.

When to use Cowork (and when not)

The shorthand: chat is for thinking together. Cowork is for working in parallel.

Use Cowork when

Stay in chat when

A useful test: if you would hand the task to a junior teammate and check back tomorrow, it is a Cowork task. If you would only hand it to them while standing over their shoulder, stay in chat.

Three tasks we run in Cowork at Waboom AI

Overnight outreach digest

Every morning at 7am, Cowork pulls activity from our Pipedrive pipeline, groups it by stage, and writes a 1-paragraph summary into a Notion page. We read it over coffee. No human touches it before 7am.

SEO check before publish

Drop a blog draft into a chat with our SEO check skill enabled. Cowork runs the 8-pass audit, flags every gap, and writes the fix list to a separate file. Six minutes of work becomes 30 seconds.

Weekly call digest from notes

Every Friday at 5pm, Cowork pulls all the meeting notes we wrote that week (saved in a specific Notion database), groups them by client, and writes a one-page summary per client. We read them over the weekend.

The three things to set up before your first task

If "set up Cowork alone" feels like too much, this is the exact runbook we cover at our Claude Code workshop in New Zealand. Operators leave with all three pieces wired up and one Cowork task already running.

Cowork is empty out of the box. Spend 15 minutes on these three setups and everything after is high-leverage.

1. Plug in your connectors

Cowork talks to your tools through Connectors. Gmail to read and draft email. Notion to read and write pages. Linear, HubSpot, Google Drive, calendar.

Settings > Connectors. Plug the two or three you actually use. We cover the full setup in Connectors 101.

2. Install one or two skills

A skill in Cowork is operational, not optional. Your branding skill governs every file Cowork creates. Your voice skill shapes every line of writing.

Start with one. We covered the full beginner course on building your first skill in Claude Skills 101.

3. Build the change-log habit

Every Cowork task you ask should end with "and write a `what-changed.md` file summarising every decision you made".

This is a Karol Zieminski rule we have adopted. Cowork makes silent decisions. The change log surfaces them so you can audit in 30 seconds.

Your first Cowork task

Pick something boring. Cowork is at its best on the work you keep avoiding.

A solid first task: "Clean up my Downloads folder."

The brief:

End state: ~/Downloads only contains files from the last 7 days.

Hand it over. Walk away. Come back to a clean Downloads folder and a one-line audit you can spot-check.

This is the gateway task. Once it works, your brain starts spotting other gateway tasks everywhere.

A note on safety

Cowork has more autonomy than chat. That means three habits matter from day one.

First, read the change log every time. Especially in the first month.

Second, never give Cowork access to a tool whose changes you cannot easily reverse. Reading is fine. Writing to your CRM, deleting files, sending email: start with read-only and graduate slowly.

Third, for any skill you did not write yourself, read the SKILL.md end to end before installing. A skill is just instructions. Bad instructions, bad behaviour.

What's next

Cowork pairs with Skills (the workflow knowledge) and Connectors (the access layer). All three together is the operating stack we teach at the workshop.

If you have not built your first skill yet, do Claude Skills 101 first. It is the building block everything else stands on.

If you want to wire up your tools next, Connectors 101 is the natural pairing.