Your First Cowork Task: Pick a Folder, Get a File Back

The fastest way to understand what Cowork actually does is to run one task and see what comes back. Not a description of what it would do. A real file, sitting in a folder on your computer. This lesson walks through that loop once, from choosing a folder to opening the result.

What Cowork can and cannot touch

Before you start, one thing worth knowing: Cowork only reads and writes files in folders you connect. It has no access to the rest of your machine. Code it runs executes in an isolated virtual machine, separate from your main operating system. So connecting a folder does not give Claude access to anything else. (Get started with Claude Cowork)

Pick a folder that already has a few files in it, or create one and drop two or three documents inside. Three Word files, a couple of PDFs, a mix. The exact content does not matter much for a first run. What matters is that the folder exists and has something in it.

Connecting the folder

When you open a Cowork session, Claude will ask which folder to connect. Point it at the folder you just prepared. That is it. You do not grant permissions file by file. The whole folder is in scope for this session, and nothing outside it is.

If you want a second folder added later, you can do that mid-session. For now, one folder is enough.

Describe an outcome, not a procedure

This is the part most people get wrong on a first run. They describe steps. “Read file A, then read file B, then create a new document with the headings from each.” Claude can follow that, but it does not need it. What works better is describing what you want to end up with.

A good starting task: summarize two or three documents in your folder into a single Word file. One heading per source document, a short summary under each, and a brief overall takeaway at the end.

A prompt that works:

“There are three documents in this folder. Create a Word file called summary.docx. Give each document its own heading and a two-paragraph summary. Add a short section at the end with an overall takeaway across all three.”

That is an outcome. Claude figures out the reading, the structure, the writing. You get back a file. (Claude Cowork)

You do not need to be more specific than that for a first task. More precise prompting, and when it matters, is covered in the next lesson.

Reading the plan before you approve it

After you submit, Claude will show you what it intends to do before it does anything. Read it. Not quickly. Actually check whether the plan matches what you asked for.

For the summarization task, you should see something like: read each document, draft summaries, compile them into a Word file with the structure you described. If it mentions doing something you did not ask for, or skips something you did ask for, say so. The plan step is a conversation. You can redirect Claude at any point before you approve. (Get started with Claude Cowork)

Once you approve, Claude works through the task. You can watch the steps as they run. If you have “Ask before acting” turned on, it pauses for your sign-off on each individual action rather than running the whole plan at once. For a first task, that setting is worth trying so you can see exactly what is happening at each stage.

What a good result looks like

Open summary.docx. You are looking for:

1. A heading for each source document, named something recognizable (ideally matching the document title or filename).
2. A summary under each heading that captures the main point of that document, not just the first paragraph.
3. An overall takeaway section that says something true across all three, not just a restatement of each summary.

If the summaries are thin, one sentence where you expected a paragraph, or if the takeaway is generic, that is fixable. Send a follow-up in the same session: “The summary for [document name] is too short. Expand it to two paragraphs.” Claude will revise the file and save the updated version back to your folder.

If it produced the wrong structure entirely, that is usually a prompt issue. The next lesson covers how to write prompts that get the structure right the first time.

If something misses

A few things that commonly go wrong on a first run:

The file does not appear. Check that the session is still active and that the task actually completed. Sometimes a task will stall without an obvious error.

The summaries are too generic. Claude may have skimmed the documents rather than reading them carefully. Adding “read the full text of each document before summarizing” often helps.

The Word file has no headings, just block text. The prompt did not specify headings clearly enough. Ask Claude to reformat it: “Add a heading for each document in the Word file.”

None of these require starting over. The session is still open. Fix it in place.

What comes next

Connecting a folder and getting back a file covers the basic loop. There is more to Cowork than this, including how permissions work, what to do with larger sets of files, and how to chain tasks together. For a fuller walkthrough of a more complex session, see how to use Claude Cowork. If you want tasks pre-built and ready to run, the workflows library has a range of starting points.

The next lesson covers writing prompts that get cleaner results with less back-and-forth.