How to Use Claude Cowork: Setup & Access Guide

Claude Cowork allows the AI to work autonomously across your local files in a sandboxed environment. You grant access to a specific folder, describe your task, and let the agent manage file organisation, document creation, and research synthesis while you focus on other work.

When Did Claude Cowork Launch?

Claude Cowork launched on 12 January 2026 as a research preview for Claude Max subscribers. On 16 January 2026, Anthropic expanded access to Pro subscribers (£16/month).

The feature builds on Claude Code, a developer tool. Accessing Cowork allows general productivity work, no terminal or coding knowledge required.

It did not stay a preview for long. On 09/04/2026 Anthropic dropped the research preview label and made Cowork generally available to all paid subscribers on macOS and Windows, shipping it with enterprise controls including role-based access control, group spend limits, usage analytics, expanded OpenTelemetry support and per-tool connector controls. On 07/07/2026 a beta extended Cowork to the web and to iOS and Android, starting with Max subscribers. In August 2026 it gained a built-in browser, and cloud memory began syncing between chat and Cowork sessions.

If you last looked at Cowork in January, the two changes that most alter how you should set it up are remote sessions and cloud execution, both covered below. Skipping straight to the download steps and ignoring those two decisions is the most common way to end up with a setup that works but frustrates you.

How to Get Claude Cowork

Getting Claude Cowork involves two main requirements: a compatible desktop machine and a paid subscription. You cannot buy Cowork separately; since April 2026 it is included with every paid plan.

How to Download Claude Cowork

Claude Cowork is not a separate app, it's built into the core Claude Desktop application.

1. Visit the download page: Go to claude.ai/download.
2. Get the Mac version: Click "Download for macOS".
3. Install: Drag the Claude.app into your Applications folder.

How to Enable Claude Cowork

Once installed, you need to activate the "Cowork" mode within the interface.

Cloud vs Local Execution: Choose First

Cowork can run the agent loop in two places, and the choice has real consequences for speed, privacy and security. Make it deliberately rather than accepting whatever the installer defaults to.

Local execution

On the desktop app, Cowork historically spun up a disposable Linux virtual machine per session using Apple's Virtualization framework, with an unprivileged user and seccomp filtering. Your files never left your machine. That is appealing for sensitive material, and it is also where the security story got complicated: on 27/07/2026, researchers at Accomplish AI disclosed a sandbox escape called SharedRoot, in which the host filesystem being shared read-write into the guest allowed a chained privilege escalation to reach files anywhere on the Mac with no permission prompt shown. Reporting placed around 500,000 users running local sessions in scope at the time.

Cloud execution (now the default)

Anthropic's response was to make cloud execution the default: the agent loop and any code it runs execute inside an isolated sandbox on Anthropic infrastructure, with no outbound network access unless an administrator allowlists it, and file access limited to the folders you authorise. This sidesteps the local escape path entirely, and it is what makes remote sessions possible — a task started on your laptop keeps running after you shut the lid.

How to Access Claude Cowork Features

With Cowork enabled, you can drag files into the window or instruct Claude to look in a connected folder to start autonomous work. Beyond the basic chat-and-files loop, there are five surfaces worth knowing about, because they are where the productivity actually comes from.

• Projects: persistent spaces that hold tasks, files and context together, so a recurring piece of work does not start from zero each time.
• Scheduled tasks: jobs that run on a schedule — hourly, daily, on weekdays, weekly or on demand. On desktop-only local runs these require the machine to be awake and the app open; with remote sessions they can run without any device online, which is the difference between a novelty and an automation.
• Connectors: integrations with services such as Google Calendar, Gmail, Notion and HubSpot, so a task can pull live data rather than only reading what you gave it.
• The built-in browser: added in August 2026, this opens a web page in a side panel and lets Claude navigate, read, click and type directly, rather than borrowing your personal browser session. It is the feature that makes research tasks genuinely hands-off.
• Skills: reusable, packaged instructions for work you do repeatedly. If you find yourself pasting the same three paragraphs of context into every task, that is a skill waiting to be written — see our guide to Claude Skills.

Connectors are the step most new users skip and most experienced users rate highest. A task that can read your calendar and your Notion workspace produces a genuinely useful Monday briefing; the same task working only from local files produces a summary of last week's documents.

How to Use Claude Cowork

File Organisation Tasks

Give Claude a messy folder and watch it sort everything logically.

Document Creation

Claude can create polished documents directly from your files and notes.

Output formats: Claude generates professional files including Excel spreadsheets with working formulas, formatted Word documents, and PowerPoint presentations.

Research & Synthesis

Combine Cowork with Claude's connectors and browser extension for research tasks.

Parallel Task Queuing

Unlike standard chat, you can queue multiple tasks and let Claude work through them simultaneously. This makes Cowork feel less like a conversation and more like delegating to a capable assistant.

Writing Instructions That Actually Work

Prompting an agent is a different skill from prompting a chatbot, and the difference is not subtlety — it is specificity about outcomes and constraints. A chat prompt can be vague because you will iterate in the next message. An agent prompt cannot, because by the time you see the result it has already moved forty files.

Say what "done" looks like

"Tidy up this folder" invites the agent to invent a definition of tidy. "Sort these files into subfolders by client name, using the client name that appears in the document header, and put anything you cannot classify into a folder called Unsorted" cannot be misread. The second instruction takes twenty seconds longer to write and saves an hour of unpicking.

State what must not happen

Negative constraints are underused and cheap. "Do not delete anything", "do not modify the originals, work on copies", "do not rename files that already follow the correct convention" are all instructions an agent will follow reliably, and all things you will wish you had said if it does not.

Ask for a plan before execution on anything destructive

For a first run on unfamiliar material, ask Claude to list what it intends to do and wait for approval before doing it. You will catch misunderstandings when they cost nothing. Once a particular kind of task has run cleanly two or three times, you can drop the approval step for it.

Give it the judgement call, not just the mechanics

The tasks where Cowork most outperforms a script are the ones involving reading and deciding: "review my draft posts and tell me which are closest to publishable, and why" or "read these forty invoices and flag anything that looks like a duplicate". Anything you could write a deterministic script for, you probably should. Save the agent for work that needs to interpret.

Break long work into checkpoints

A ten-step task that runs unattended and fails at step eight has wasted eight steps. The same task expressed as three phases with a verification point between each fails at the end of phase two, and you correct course having lost far less. Anthropic's own usage data suggests this is how the tool is mostly being used in practice: business process and operations work accounted for 33.4% of Cowork usage in its sampled figures, with content creation at 16.4% and software development a distant 8.7%.

Desktop, Web and Mobile

Until July 2026 Cowork was a desktop product with a desktop product's limitations: close the laptop and the work stopped. The web and mobile beta announced on 07/07/2026, opening first to Max subscribers, changed the execution model rather than just adding screens.

Remote sessions run on Anthropic's servers and are saved to your Claude account, so a task continues with no device online at all, and scheduled work fires whether or not your machine is awake. The practical consequence is a genuinely different working rhythm: you start a piece of research on the desktop before lunch, get a notification on your phone when it needs a decision, approve the next step from the platform queue, and find the finished document waiting when you sit back down. Files sync across devices, and sessions can be resumed from whichever surface you happen to be at.

Two caveats. First, this is a beta and started with the highest tier, so availability on your plan may lag what you read about. Second, remote sessions and local file access are in tension by definition — a session running on Anthropic's infrastructure is working with what you have synced, not with whatever is sitting on your desktop right now. For file-heavy work rooted in a local folder, the desktop app remains the primary surface, with mobile acting as a remote control rather than a replacement. Our guide to Cowork on mobile goes into what does and does not carry over.

Requirements & Eligibility

Who Can't Use Claude Cowork?

This list has shrunk considerably since launch. As of the April 2026 general availability release, Cowork is included with all paid plans on macOS and Windows. What remains:

• Free plan users — there is no permanent free tier for Cowork itself
• Linux desktop users — there is no official app
• Anyone needing full local-folder work from web or mobile alone; those surfaces are built around remote sessions rather than direct access to your drive

Usage Limits

Cowork tasks consume significantly more of your usage allocation than regular chat. A complex multi-step task might use as much quota as dozens of standard messages. Pro users will hit limits faster than Max subscribers — the Max 5x and 20x tiers are named for their usage multiple relative to Pro, not for any difference in capability.

The practical consequence is that the way you phrase a task has a cost, not just a quality, dimension. An agent asked to "read everything in this folder and summarise" will read everything in the folder. Narrowing the scope, splitting long jobs into phases, and pointing the agent at the ten files that matter rather than the hundred that exist are the habits that keep a Pro plan viable. Our Cowork pricing guide sets out the tiers in detail.

Troubleshooting & Common Mistakes

Claude says it cannot see a file that is clearly there

Almost always a scope problem rather than a bug. Cowork can only reach folders you have explicitly connected, and it does not follow a path outside that boundary just because you pasted one. Check which folder is connected, and remember that an alias or symlink pointing outside the connected folder resolves to somewhere the agent is not allowed to go.

A task stops halfway and waits

This is usually the checkpoint system working correctly: the agent has hit something it judged needed a human decision. On desktop this is visible immediately; with remote sessions it arrives as a notification, and the session resumes once you respond. If nothing appears to be waiting and nothing is progressing, check whether you have hit a usage limit — quota exhaustion mid-task is one of the less obvious failure modes.

The output is right but formatted wrong

Give it an example. Dropping a correctly formatted document into the connected folder and saying "match this" is dramatically more effective than describing the format in prose. If the same formatting requirement recurs, promote it to a skill rather than restating it each time.

It did something you did not ask for

Agents fill gaps in instructions with plausible assumptions. Re-read what you actually wrote — in most cases the instruction admitted the behaviour. Add the missing negative constraint and re-run. If it genuinely went beyond a clear instruction, that is worth reporting rather than working around.

Results differ between desktop and web

Expected. A remote session works with what has synced to your account, not with the live state of your local drive. If a task depends on a file you saved thirty seconds ago, run it where that file is.

Working Safely with an Agent on Your Files

Cowork is the first tool many people will use that can modify their filesystem without a human confirming each action. That deserves a few habits.

• Connect a working folder, never your home directory. Create a dedicated folder, copy in what the task needs, and let the agent work there. The blast radius of a misunderstanding is then exactly the size you chose.
• Work on copies for anything irreplaceable. Cloud-synced folders with version history are your friend here; so is a five-second duplicate before a destructive-sounding instruction.
• Be deliberate about connectors. A connector that can read your inbox has meaningfully expanded what a badly-scoped prompt can surface into a document. Grant the ones you need for the task in front of you, and use per-tool connector controls if your organisation provides them.
• Treat web content as untrusted input. Once an agent is reading web pages and acting on what it finds, prompt injection stops being theoretical. Be cautious about combining broad web access with write access to sensitive folders in the same session. Claude in Chrome shipped with prompt-injection safeguards when it reached general availability in August 2026, which tells you the risk is taken seriously rather than that it is solved.
• Review before you forward. An agent-produced spreadsheet looks exactly as authoritative as a human-produced one. Spot-check the numbers before it goes to a client.

None of this is a reason to avoid the tool. It is the same care you would take with a capable new colleague on their first week: give them a defined scope, check the first few pieces of work, and widen the remit as trust is earned. If you are still weighing Cowork against the alternative in your organisation, our comparison of Claude Cowork and Microsoft Copilot covers where each one fits.

Free Guide

Get the free guide: Claude vs ChatGPT, Gemini & Grok

A 20-page playbook covering everything you need to choose and use the big four AI models in 2026, full cost and feature comparisons, what each is best (and worst) at, and how-tos for images, vectors, building a website, Claude Code and more.

Pop your email in to get it free

Download free guide Email me the guide and occasional AI tool insights. No spam, unsubscribe anytime. See our privacy policy.