Your first 30 minutes with Cowork

TL;DR. End your first half-hour with a real artifact, not a tour of the menus. Install, grant a folder, run two prompts — one to organise, one to produce — and you will have shipped something useful before the kettle boils. The single habit to internalise: read the plan before approving.

The 30-minute timeline#

• 0–5 min — install Claude Desktop and enable Cowork.
• 5–10 min — create the workspace folder, drop in two real files.
• 10–20 min — run your first prompt: organise the inbox.
• 20–30 min — run a second prompt that ships an actual artifact (a one-page summary).

If you have not made the pre-flight decisions yet, do those first. They take half an hour; they save weeks.

0–5 min — install and enable#

1. Download Claude Desktop from claude.ai/download. Install it like any other app.
2. Sign in with the same Claude account you use on the web.
3. Open Settings → Features and toggle Cowork on. Approve folder access only when prompted in the next step — not pre-emptively.
4. Confirm you have a Pro, Max, Team, or Enterprise plan. Free accounts cannot use Cowork.

If you see Chat and Code tabs but no Cowork tab, the toggle has not flipped — go back to Features.

5–10 min — workspace and seed files#

Create one folder for this exercise:

mkdir -p ~/cowork-firstrun/inbox ~/cowork-firstrun/output

Drop two real but non-confidential documents into inbox/. A recent supplier PDF, a slide deck draft, a Word doc — anything you would handle in a normal week.

Back in Cowork, click Grant folder access and select ~/cowork-firstrun/. Only this folder.

The first time Cowork sees a folder it will index the files quickly. You will see the file list appear in the sidebar; that is your signal Cowork is ready.

10–20 min — your first prompt: organise the inbox#

Copy and paste this verbatim:

Look at the files in ~/cowork-firstrun/inbox.
Plan first. Show me a one-line summary of each file
and a proposed folder structure (by document type) before doing anything.
After I approve, move the files into the new structure
and write a short manifest called inbox-manifest.md inside ~/cowork-firstrun/output.

Watch what happens.

Cowork should respond with a plan — a list of files, summaries, and a proposed folder structure. It should not have moved anything yet. Read the plan. If it looks right, approve. If it does not, push back in plain English: "don't move PDFs into a 'misc' folder; create a 'supplier' folder for them."

Once you approve, Cowork executes and writes the manifest. Open inbox-manifest.md and verify.

This is the single most important Cowork habit: read the plan, push back, then approve. Internalise it now. Skipping the plan is the cause of most "Cowork did the wrong thing" complaints we see in the wild.

20–30 min — your first artifact: a real one-pager#

Now produce something you would actually send to a colleague.

Take the first PDF in ~/cowork-firstrun/output/supplier
and write a one-page summary in plain English for an executive who has 90 seconds.
Include: what the document is, the three things that matter,
the deadline if any, and one open question I should ask the supplier.
Save as ~/cowork-firstrun/output/[filename]-summary.docx.

A few things to notice:

• Cowork creates a .docx directly. Open it in Word — it lands cleanly in Microsoft 365.
• Compare against the source PDF. Did it miss anything material?
• Iterate conversationally: "make the open question sharper" or "shorten by 20%" or "add a 'next steps' line at the end."

The point of this slice is to feel the iteration loop, not to produce a perfect summary on the first pass.

What you just learned#

• Cowork plans before acting. Read the plan.
• It works on one folder, not the whole laptop. That is by design.
• Office formats are first-class output, not an afterthought.
• Iteration is conversational. Tell it what to fix.

These four habits cover 90% of what makes a Cowork user productive in week one.

Five things to try next, in priority order#

1. Build a folder for your real role — not a test folder. See The workspace pattern.
2. Add a CLAUDE.md to that folder with house rules. See CLAUDE.md and memory.
3. Try a prompt from the Document generation prompts library.
4. Try a multi-file research prompt. See Research prompts.
5. Read the security basics so you do not accidentally feed Cowork something you shouldn't. See Security model.

Tinkso's take#

We run this exact 30-minute exercise with every new user in every deployment. The framing matters — "ship something real in 30 minutes" — because Cowork's value compounds when the first session produces an artifact, not when it produces a tour of the menus.

The temptation in the first session is to test the limits ("can it read this CAD file?"). Resist. Limit-testing comes in week two. Week one is about the loop: read the plan, push back, approve, iterate.

Try this — a prompt worth keeping#

Save this in your CLAUDE.md so future sessions inherit it.

Read [filename]. Summarize for an executive in <120 words.
Include: what it is, three things that matter, deadline, one open question.
Plain English. No marketing language.

This is the single prompt we have seen survive across the most engagements without modification. Make it yours.