Getting Started with Claude Cowork: Hand Off Work to Finished Deliverables on Desktop

Claude chat is great for drafts and summaries, but asking it to “organize this folder” or “build the weekly brief” often turns into a long back-and-forth. Claude Cowork is the on-ramp for applying AI you hand work to to personal knowledge work.

Officially, Cowork is described as a surface where you hand over a goal, Claude works across files and tools, and you get reviewable deliverables back (Claude Cowork, Get started with Claude Cowork). Think of it as the same family of agent infrastructure as Claude Code, aimed at work beyond coding.

What you’ll learn in this article:

• What Cowork is, and how it differs from Chat, Claude Code, and Claude Tag
• When to use Desktop vs. web vs. mobile (especially when local files matter)
• A template for your first task request, plus examples of work that fits
• Caveats around scheduled tasks, approval modes, and usage limits

Availability (official): Paid plans (Pro / Max / Team / Enterprise). Cowork on web and mobile is in beta (Enterprise requires an admin to enable it for the org). Features, plans, and beta scope change often—check official help before you decide to roll it out.

Claude CoworkClaude Cowork

A Claude work surface for multi-step jobs with a clear deliverable. It can use folders you point it at, connectors, the browser, and more, then return output you can review. Officially framed as an agentic (delegated) way of working.

How it differs from Chat

The official tutorial draws the contrast like this (Choosing between Claude Cowork or Chat):

Lens	Chat	Cowork
Goal	Still figuring it out together	You can name the deliverable
Work shape	Short back-and-forth	Multi-step, multi-source, longer running
Your role	Present every turn	Hand it off, check back later
Output	Text you read or copy	Finished files or completed actions

Short version: Brainstorm in Chat. Want finished work? Use Cowork.

How Cowork relates to Code and Tag

“Handing work off” shows up in more than one place—the location and who can see it differ.

Lens	Cowork	Claude Code	Claude Tag
Main jobs	Research, docs, sheets, cleanup	Implementation, debugging, PRs	Shared team handoffs
Where	claude.ai / Desktop / mobile, etc.	Terminal, IDE, etc.	Slack channels
Who sees it	Mostly you	Mostly you	Channel members
Best for	Knowledge work, including non-engineers	Developers	Team/Enterprise orgs using Slack

For Slack-based team handoffs, see What is Claude Tag?.

Choosing Desktop, web, or mobile

Official help says Chat and Cowork share the same home, and sessions stay tied to your account across surfaces (Use Claude Cowork on web, desktop, and mobile).

Surface	Best fit (per official guidance)
Desktop	The full experience: local folders, built-in browser / Chrome integration, computer use
Web / mobile (beta)	Start, monitor, and review work that uses connectors and cloud context. Local reach still goes through the Desktop app
Chrome side panel	Opening the panel can start a Cowork session (depends on plan and rollout)

Important notes (official):

• Cloud sessions can keep going even if you close your laptop
• Local files, local connectors, browser control, and computer use require the Desktop app to be open (including when you kick them off from web/mobile)
• Scheduled tasks generally run in the cloud and can run while your device is off. Help also notes that schedules tied to folders on your PC can depend on the local machine

So “deliverables on desktop” isn’t marketing fluff—work that touches local files or the screen is centered on Desktop, per how Anthropic draws the line.

Getting started

1. Sign in to Claude on a paid plan
2. For Desktop, install the latest build from claude.com/download (Windows guidance calls out needing the latest version)
3. In the message composer, choose Cowork (toggle vs. Chat)
4. Put deliverable, materials, constraints, and review criteria into one clear request
5. Watch the plan and steps; steer mid-run if needed
6. Have a human review before anything goes external or to production

A request skeleton close to official examples:

Read the invoice PDFs in Downloads, sort them into YYYY-MM folders, and create an expense-summary xlsx in the same place. Don’t delete anything. Move unclear files only into _needs-review.

Work that fits well

Help-center categories, restated for day-to-day knowledge work:

• File cleanup — sorting Downloads, normalizing names, turning a receipts folder into an expense sheet
• Research synthesis — web, notes, and multiple PDFs into one internal memo
• Document drafting — meeting notes into slides; scattered notes into a report
• Spreadsheet work — reconciling multiple exports; an xlsx with diff flags
• Scheduling — morning briefings, weekly channel-metric drafts (connectors assumed)

Product-page scenarios like “Monday marketing readout” or “first-pass contract review” are Anthropic demo stories. Don’t treat them as a guarantee of the same accuracy on your data.

How to use scheduled tasks

In Cowork you can register recurring or on-demand runs from the Scheduled sidebar or from the in-task scheduling flow (Schedule recurring tasks in Claude Cowork).

Official highlights:

• Aimed at paid plans
• Cloud execution is the default; runs can continue while the device sleeps
• Expects connectors and account-side files
• Help notes that recurring runs bound to a specific folder on your PC may depend on the local machine

Good first candidates look like “every morning, bullet only what’s still open from connected email/Slack”—low blast radius, human-readable drafts.

Setting permissions and safety boundaries

Cowork can read/write files and operate connectors—real work, not just text. Official guidance pushes you to read the safety materials.

Boundaries worth deciding up front:

• Minimize which folders/connectors it can touch
• Deletion requires explicit approval per official behavior—still don’t ask for “cleanup = delete”
• External email, customer outreach, and production changes stay human-approved
• For important work, start approval mode closer to Manual (confirm each step)
• Auto mode is faster with safety checks, but official guidance still says stay close / switch to Manual for money, sending, or critical files

On Team / Enterprise, admins can control Cowork on/off, cloud execution, and some auto-approval options. Check company policy before you connect production data to a personal Pro account.

What to do in the first week

1. Pick one “graduate from Chat” task (e.g., a weekly memo draft)
2. Connect a single folder in Desktop and try it
3. Run the same request twice and notice output variance
4. If it holds up, move it to Scheduled or save a template prompt in your wiki
5. If the team needs shared visibility, split that work to Tag (when you’re eligible)

For the broader framing, pair this with AI you hand work to; for Slack sharing, see What is Claude Tag?.

FAQ

Q.Can I use Cowork on the free plan?

Official guidance positions it for paid plans (Pro / Max / Team / Enterprise). Confirm on your account screen and the pricing page.

Q.Do I always need the Desktop app?

Cowork is also available in beta on web and mobile. Official help says work that touches local folders, browser control, or computer use still needs the Desktop app. Safest mental model: full experience = Desktop.

Q.Should I start with Cowork or Claude Code?

If code changes are the main job, start with Code. If docs, sheets, research, and cleanup dominate, start with Cowork. That split matches official positioning—you don’t need both.

Q.Do tasks keep running if I close my laptop?

Officially, cloud sessions and scheduled tasks can continue with the device off. Work that depends on local files or the browser needs the Desktop app left open.

Q.What if I want to collaborate in a team channel?

Personal handoffs → Cowork. Shared handoffs in Slack → Claude Tag (Team/Enterprise beta). See the Claude Tag article for details.

Bottom line

Claude Cowork is the step past Q&A Chat: hand off through a deliverable, then review as a human. Even within the same agent family, Code is for software work, Tag is for shared team work, and Cowork is for personal knowledge work—that split makes adoption stick.

Your first win isn’t a giant automation. It’s one folder, one deliverable, and a human review. Once you’ve done a Desktop run that touches local files, it’s much easier to leave “stuck in chat” behind.

Sources

1. Get started with Claude Cowork（Anthropic Help Center）
2. Use Claude Cowork on web, desktop, and mobile（Anthropic Help Center）
3. Schedule recurring tasks in Claude Cowork（Anthropic Help Center）
4. Choosing between Claude Cowork or Chat（Anthropic / Claude）
5. Claude Cowork (product page)（Anthropic）