Anthropic's Claude Cowork is temporarily doubling usage credits for all paid users — Pro, Team, and Enterprise are all covered — with the promotion running until early July 2026. Alongside it, the official team released a 23-page product guide covering 7 major work scenarios. This tutorial pulls out the core scenarios and operational tips to help you get up to speed fast.

What Is Claude Cowork

Cowork runs inside the Claude desktop app (both macOS and Windows), and it differs fundamentally from chat AI like ChatGPT or Gemini: instead of manually feeding it materials, you grant it access to a local folder, and it digs through the files itself, connects to Slack and Gmail, and saves the finished work back on its own.

In short: you describe the outcome, it executes the process.

The Double-Credits Details

• Coverage: all paid users on Pro, Team, and Enterprise
• The 5-hour usage limit is directly doubled, for one month (ending in early July 2026)
• Pro users pay $20/month, and heavy use in one month consumes roughly $236 worth of compute — a subsidy ratio of 12:1

Tip: If you don't have a Pro subscription yet, $20/month makes this the best time to jump in.

Scenario 1: Weekly Reports in One Sentence

Every Friday you assemble your weekly report from three places (an Asana board, a data CSV, a Slack channel) — at least an hour of manual work. With Cowork, one sentence does it:

Draft this week's engineering weekly report following the format of ~/Reports/weekly-template.md.
Pull delivered items from Asana's "Done This Week" board,
pull key metrics from ~/Reports/metrics.csv,
and pull blockers since Monday from the #eng-blockers channel.
Save it as weekly-update-2026-06-06.md.

Behind that sentence, three layers of capability are at work:

• Local file read/write: it goes straight to your hard drive for the template and CSV — no uploading needed
• MCP connectors: it connects to Asana and Slack over the MCP protocol, reading three data sources in a single prompt
• Scheduled tasks: save that prompt as a template and set it to run automatically every Friday morning

Tip: Save your frequently used prompts as templates and turn them into scheduled tasks — your weekly report will already be sitting in the folder before you've reached your desk.

Scenario 2: Smart Email Triage

You come back from a long weekend to 120 unread emails. Use this prompt to sort them automatically and draft replies:

Go through my unread Gmail from the past 72 hours.
Sort each thread into four buckets:
"Must reply today", "Can wait a week", "FYI only", "Forward to [boss's name] to handle".
For each "Must reply today" email, start a separate file with a two-sentence reply draft.
Do not send. Draft only.

Permission design is the key here: Cowork won't send any email without your nod — the drafts are written and left there for you to confirm one by one.

Note: Beginners should run a few rounds in the default permission mode before turning on "Act without asking."

Scenario 3: Parallel Multi-Document Comparison

You have five vendor PDF proposals to compare side by side:

There are five PDFs in ~/Vendors/proposals.
From each one, extract pricing, deployment timeline, what is included, extra fees, SLA, and reference cases.
Generate an xlsx comparison table, then write a short recommendation,
clearly stating which two vendors should make the shortlist and why.

Cowork automatically spins up "parallel sub-Agents," splitting the five PDFs across multiple sub-agents that read them simultaneously, each extracting information that is then consolidated. Where information is missing, it flags it directly rather than guessing.

Scenario 4: Folder-Level Bulk Reading

Three weeks of industry research is scattered everywhere, and a competitor brief is due tomorrow:

I have connected the ~/Research/competitive-landscape folder.
Read everything in it and write a two-page brief
covering the three most important trends, what each competitor is doing,
where our biggest weaknesses are, and two recommendations.
Cite the source file for every conclusion. Save it as competitive-brief.md.

The most valuable capability here is "traceable citations": every conclusion traces back to a specific source file, so whenever you're unsure about a claim, you can click through the reference to the original text.

Tip: When a folder is especially large, ask Cowork first to report how it plans to read it, review that, and only then let it proceed. Correcting course early beats cleaning up a mess later.

Scenario 5: Notes to Project Plan

Scrawled notes from a meeting, turned into a structured project plan in one sentence:

Read ~/Projects/website-redesign/kickoff-notes.md.
Turn it into a project plan with milestones, a task breakdown under each milestone,
owners assigned based on the names mentioned in the notes, a rough timeline assuming a six-week delivery, and a risk list.
Output both a markdown document and a CSV.

It outputs both formats at once: Markdown for humans to read, CSV to import into project management tools. Where things are ambiguous, it produces an "ambiguity list" telling you what it guessed.

Scenario 6: Fast Meeting Prep

You meet a client in 90 minutes, and the context is scattered across four places:

I have a Q3 partnership review with Sarah Chen from Acme at 2 PM.
Pull together her recent email threads in Gmail, our last two Slack DMs,
the shared Doc titled Acme partnership Q3, and the calendar notes from our last meeting.
Give me a one-page prep doc listing the three things I must know and two questions I should proactively raise.

You tell it where to look; it connects to Gmail, Slack, Drive, and Calendar itself, pulls what it needs, cross-references everything, and writes the conclusions up into a saved document.

The Key to Writing Good Prompts

The more specific the prompt, the more directly usable the work it hands back. "Help me prep for a meeting" is a wasted prompt. Names, data sources, output format, how many points — the more precise, the better.

Reference structure: goal + where the data lives + output format + where to save it

FAQ

• When do credits reset? It's a rolling 5-hour window; after doubling, the window's capacity doubles, and it reverts once the promotion ends in early July.
• Cowork vs. Claude Code? Claude Code targets programming scenarios; Cowork targets the daily work of all knowledge workers.
• Which systems are supported? Both macOS and Windows — you need the Claude desktop app.
• Does MCP need extra setup? Connecting services like Slack, Asana, and Gmail requires enabling the corresponding MCP connectors in settings.

References

• Official product guide PDF
• Claude official blog