What Is Claude Cowork? A Practical Guide to Files, Browsing and Recurring Work
Last verified: September 16, 2026. Based on official documentation, not a hands-on product benchmark.
Cowork is worth evaluating when a task involves more than answering a question: reading several inputs, organizing the evidence and preparing something another person can use. A meeting brief, a comparison memo or a reporting draft can be a better first test than a vague request to “automate my job.”
The goal is not to eliminate oversight. It is to reduce mechanical preparation while keeping the important decisions visible.
What Cowork adds
Anthropic positions Cowork as an agentic environment for knowledge work beyond coding. Think in terms of a task and its deliverable, rather than a sequence of unrelated chat replies. Getting started.
Before beginning, define the intended reader, required sections and what counts as evidence. A polished document can still be wrong if it invents a deadline or turns a suggestion into an agreed decision.
Try this original MSL prompt:
Turn these meeting notes into a one-page brief for someone who could not attend. Separate decisions, open questions and next actions. Mark missing owners and deadlines as unspecified. Do not invent agreements. Prepare a draft only; do not distribute it.
Check a few statements against the notes before refining the styling.
It is no longer simply desktop-only
Current documentation describes Cowork on desktop, web and mobile, with web/mobile in beta on eligible paid plans. Cloud sessions can continue across devices, but local resources remain conditional. Device guide.
The key distinction is between work that can continue remotely and access to something that exists only on your computer. Do not assume closing the laptop leaves local files reachable. Check desktop connection and session requirements before relying on that workflow.
For a first trial, use a dedicated folder containing fictional documents. Ask for a file inventory and proposed organization before allowing any moves or renaming. That lets you evaluate the classification without risking your originals.
Two browser approaches
Anthropic documents a built-in desktop browser and Claude in Chrome. The former uses a separate browsing environment; the latter works through your Chrome setup. Availability is rolling out, and authentication should not be assumed to transfer between them. Browser guide.
Desktop requirements differ by browser route. The general device guide and the browser-specific guide describe conditions and exceptions differently, so confirm the exact route you intend to use instead of assuming web or mobile browsing is fully independent of a desktop.
A sensible first task is gathering public information into a reviewable list. Keep purchases, account changes and sensitive information outside that trial.
Recurring tasks: useful, but test the inputs
Cowork supports scheduled work, with official guidance describing cloud execution. The scheduling article contains mixed wording about local-folder support, so this guide does not promise unattended access to files on an offline computer. Scheduling guide.
An editorial example:
Every Monday at 9 a.m. in my specified time zone, review these three official sites. List changes since the previous run, the update date, source link and likely relevance. If nothing changed, say so. Save a review draft and do not publish or contact anyone.
Check the next-run time, time zone, inputs and destination. Run it manually once. Creation of a schedule is not evidence that the first scheduled run succeeded.
Recent changes worth knowing
Anthropic’s August 25 notes describe memory spanning chat and cloud Cowork. Its September 15 notes announce a Salesforce beta with approval conditions, not universal access. Treat these as dated product updates rather than features guaranteed to every subscriber. Release notes.
For everyday work, the practical lesson is to inspect both context and permissions. Useful remembered information can still be outdated for a new project.
Pricing and an economical trial
Claude Pro includes Cowork and is listed at US$20 monthly or US$200 billed annually. This is a Claude subscription, not a separate Cowork-only fee. Taxes, additional usage and account conditions need checking at purchase. Official pricing.
Use ordinary chat when you only need a short rewrite. Evaluate Cowork on work with multiple inputs and a specific deliverable. Track review effort as well as execution time before deciding whether a higher plan is justified.
Three tests for your first week
| Sample input | Requested output | What to check |
|---|---|---|
| Anonymous meeting notes | Decision and action brief | No invented owners or dates |
| Public product documentation | Conditional comparison memo | Correct dates, plans and exclusions |
| Fictional marketing results | Summary and improvement hypotheses | Reconciled totals; no causal claims from correlation alone |
These are evaluation suggestions, not performance promises. Repeat one task with different inputs to learn whether the method holds up.
Common questions
Is Cowork the same as Claude Code? No. Do not choose solely by the underlying model name; evaluate the product workflow you need.
Can I give it a folder and let it reorganize everything? Begin with an inventory and a proposal. Keep moving, overwriting and deleting as separate authorized steps, with a backup.
Can it run every business process automatically? Connections, authentication, admin settings and device dependencies can prevent completion. Test a complete low-risk run before scheduling it.
Cowork is most useful when it turns a defined set of inputs into something you can inspect. Limit the input scope, require evidence and decide where human approval belongs. Those habits make it easier to judge real value without confusing a convincing demo with a reliable process.
MSL practice exercise: preserve uncertainty in meeting notes
MSL created the fictional input below. It is not an observed Cowork response. Establishing an answer key first makes it easier to detect a polished summary that silently changes the meaning.
A short fictional meeting note
Proceed with a 30-second concept for the new product video. Someone suggested a vertical format. Sato said, “I can help with editing.” The release date will be decided next time. The price needs confirmation from its owner. The next meeting is next week; the weekday is undecided.
Answer key for this input
| Item | Supported statement | Unsupported addition |
|---|---|---|
| Duration | Proceed with a 30-second concept | The final video duration is confirmed |
| Vertical format | A suggestion | A finalized 9:16 specification |
| Editing owner | Sato offered help | Sato was formally assigned ownership |
| Release date / price | Undecided / requires confirmation | A specific date or amount |
| Next meeting | Next week, weekday undecided | A specific weekday |
A reusable evaluation prompt
Use only these notes to prepare a meeting brief. Separate decisions, suggestions, unresolved items and confirmation questions. If an owner, deadline or price is not explicit, mark it undecided or requiring confirmation. Attach a short supporting excerpt to each item. Prepare a confirmation email draft only; do not send it.
My adoption criterion: the output separates suggestions from decisions, preserves unknowns and can be traced back to the input. If it invents an owner or date, I would revise the task and reassess before using it in real work. Clear remaining questions matter more than length or decoration.
Start with material that contains no personal information. Before using actual work documents, check your organization’s handling rules and the conditions of the chosen environment.
Original MSL exercise prepared October 14, 2026. Not a hands-on product benchmark.
Official sources
- Get started with Claude Cowork
- Cowork on web, desktop, and mobile
- Built-in browser
- Recurring tasks
- Release notes
- Pricing
From the publisher: how I would decide
I would begin with one meeting brief, not a promise to automate the entire office. My first check would be whether missing owners and deadlines stay explicitly missing. A polished report becomes less useful if it silently invents agreement. Recurring work interests me only after the one-off task produces something I can trace back to the source. For MSL, I would judge Cowork by how clearly it exposes the remaining decisions, including which inputs depend on a connected desktop.
