Your first Cowork task

The goal of a first task is not to be impressed. It is to build an accurate sense of what this thing does when you are not watching, before you rely on it.

Set it up

Open Claude on desktop, web or mobile and choose Cowork from the message box. On desktop, keep the Claude Desktop app open — local file access runs through it.

Then connect a folder. Make it a duplicate of a real project folder rather than the original, and make it the narrowest folder that contains the work. See Undo, blast radius, and working on copies for why this is not optional caution.

Leave approval on Manually approve for the first run. You want to see what it intends to do while you still have opinions about it.

Pick the right task

A good first task is multi-step, has a checkable answer, and touches nothing you would mourn.

Good candidates:

• Read a folder of documents and produce a summary table of a few fields you can spot-check.
• Take a messy set of notes and turn them into one structured document.
• Pull figures from several files into a single comparison.

Bad candidates: anything with one-paragraph output — that is a chat. Anything touching financial documents, credentials, or client data on a first run. Anything you could not check.

Describe an outcome, not a procedure

Say what "done" looks like and what constraints matter. Leave the method to it.

Read every PDF in this folder. For each one, pull out the client name, the contract end date, and the notice period. Put them in a single markdown table sorted by end date. If a field is missing or ambiguous, write "unclear" rather than guessing, and list those files separately at the bottom.

The last sentence is the one that earns its place. Without it, ambiguity gets resolved silently and confidently, and you will not know which rows to distrust.

Watch the first run

Cowork shows its reasoning and each step as it goes. On the first task, read it. Not to supervise every action — to learn what its step trail looks like when things are going well, so that later you can recognise when they are not.

You can steer mid-task. If it heads somewhere wrong, say so rather than letting it finish and fixing the output.

What goes wrong

Choosing a task too small to be informative. "Rename these files" tells you nothing about judgement. You want something where it had to decide things.

Pointing it at the real folder because copying felt paranoid. The first run is exactly when you know least about how it behaves.

Reading the summary instead of the work. Claude's account of what it did is generated the same way everything else is. Check the output against the sources.

Burning your allowance on the first afternoon. Cowork consumes noticeably more usage than standard chat. Watch Settings → Usage while you experiment; the rate will surprise you once.

How to check it worked

Take three rows of whatever it produced and verify them against the original files yourself. Then look specifically at the cases it flagged as unclear — if that list is empty on genuinely messy input, it resolved ambiguity silently, and that tells you more about the run than the ninety rows that look right.