How to Use Claude Cowork: A Step-by-Step First Task

The fastest way to understand Claude Cowork is to give it one real job and watch it finish. Run through this walkthrough once and you’ll have both a completed task and the small habits that separate a smooth session from a frustrating one.

This assumes you already have access to Cowork in the Claude desktop app. If you’re not sure what it is yet, read what Claude Cowork is first.

Step 1: Choose a working folder

Cowork does its best work when it has a folder to operate in. This is the single most important setup step, and it’s the one people skip.

When you open a Cowork session, you’ll be prompted to select a folder on your computer. Pick a real one: a project folder, a folder of documents, wherever the relevant files live. Cowork can read everything in that folder and write new files back to it.

Treat the folder like a desk you’re sharing with someone. Anything on it is fair game; anything off it is out of reach. That boundary is what keeps the tool safe to run on a real machine.

If you just want to experiment first, make a throwaway folder with a couple of sample files in it.

Step 2: Describe the outcome, not the steps

Here’s the mindset shift. In a normal chat you ask questions. In Cowork you describe a finished result.

Instead of “how do I summarize these documents,” try:

“Read the three PDFs in this folder and write me a one-page summary as a Word document, with a short section for each.”

The difference matters because Cowork will go and do that: open the files, extract the content, build the document, save it. A vague request gets a vague plan. A specific outcome gets a specific file.

Step 3: Let it plan, then approve

For anything beyond a trivial request, Cowork will outline what it intends to do before it does it. Read the plan. This is your chance to catch a misunderstanding before any work happens, not after.

You’ll also see it ask permission before anything irreversible: deleting, overwriting, or renaming existing files. Don’t rubber-stamp these. The approval step exists so you stay in control of your own files.

Step 4: Watch the work happen

As Cowork runs, it shows what it’s doing: reading a file, running a calculation, searching the web, building a document. You don’t need to understand every step, but skimming them tells you whether it’s on track.

If it heads in the wrong direction, stop and redirect. There’s no reason to let it finish a doomed attempt.

Step 5: Collect your files

When the task finishes, Cowork hands back the completed files and they’re saved in your working folder. Open them the way you’d open anything else. This is the moment the tool earns its name: you asked for an outcome and you got the artifact, not a transcript.

A realistic first task to try

This one shows off what Cowork is good at without being risky:

1. Make a folder and drop in two or three documents you actually need summarized: meeting notes, a report, an article.
2. Open Cowork, select that folder.
3. Ask: “Summarize each document in this folder into a single Word file. Use a heading per document, three bullet points each, and a short overall takeaway at the top.”
4. Approve the plan, watch it work, and open the result.

You’ll immediately feel where it’s strong (assembling and formatting) and where you still need to review (judgment calls, tone, a fact you happen to know is wrong).

Five habits that make it reliable

After enough sessions, a few patterns pay off consistently:

• Be specific about format. “As a spreadsheet with columns for date, vendor, and amount” beats “in a table.”
• Give it the source, don’t paraphrase it. Point it at the file rather than retyping what’s in it. More accurate, far faster.
• Work in one folder per project. It keeps the context clean and the outputs where you expect them.
• Review before you send. Cowork handles the first 90% of document work well. The last 10%: judgment, tone, a fact you know is wrong. That part is still yours.
• Save the prompts that work. When a request produces a great result, keep it. You’ll reuse it more than you expect, and it’s the seed of a scheduled task.

When something goes wrong

Two issues come up often enough to mention. If Cowork can’t see your files, check that you selected the folder they’re actually in, not its parent and not a sibling folder. And if a task stalls or errors out, the fix is usually to restate the request more specifically, not to retry the same wording and hope harder.

Next steps

Once the first task clicks, the natural move is to make Cowork more capable by connecting it to your other tools. That’s what plugins and connectors are for, and where the real time savings start to compound.

For a step-by-step path from scratch, take the free Claude Cowork course. For the big picture, see our complete guide to Claude Cowork.