Cloud vs Local Sessions in Claude Cowork

Claude Cowork runs cloud sessions by default: planning and tool use happen in isolated Anthropic-managed environments, and sessions and files are saved to your Claude account. Existing desktop deployments may still use local execution, but that is not the same as “data never leaves your machine.” Any step that needs a folder, browser, or app on your computer still requires Claude Desktop to stay open and connected.

Definitions you can quote

Cloud-default session: Cowork runs the agent loop remotely in an isolated sandbox. Work that only needs web research, connectors, plugins, skills, or files already saved to your Claude account can continue even if your laptop sleeps.

Local / desktop-connected work: Steps that touch a folder on your computer, your browser, or a desktop app require Claude Desktop on that machine. The desktop connection—not “local-only privacy”—is what makes those resources available.

Account-saved artifacts: Anthropic’s Cowork help and architecture guidance describe sessions and files as saved to your Claude account. Do not assume task content stays only on the device.

Cloud-default sessions vs desktop-connected work

Aspect	Cloud-default session	Local / desktop-connected work
Where the agent loop runs	Anthropic-managed isolated environment (default, still rolling out)	Existing desktop deployments may keep local execution
What it can use without Desktop	Web research, connectors, plugins/skills, files saved to your Claude account	N/A — local resources need Desktop
What needs Claude Desktop	Local folders, browser, desktop apps, Computer Use	Same resources; Desktop must remain available for those steps
Laptop closed / asleep	Remote-only steps can continue; desktop-dependent steps wait	Local session work stops when the device is unavailable
Privacy framing	Sessions and files are saved to your Claude account; remote processing applies	Still not “never leaves the machine”—task content is processed as part of the session
Best for	Research, synthesis, account files, remote scheduled work	Organizing a local folder, desktop apps, Dispatch to an awake PC

When Claude Desktop must stay open

Keep Claude Desktop open and the computer available when the task needs any of the following:

A folder on the machine (read, write, move, organize)
Your browser or a desktop application
Computer Use (screen and app control in research preview)
Dispatch assignment to that computer (Desktop must stay open; the machine should stay awake)
A local scheduled task that was configured to use on-device folders or apps

If a cloud session only needs remote tools and account files, closing the laptop does not cancel those remote steps. Desktop-dependent steps resume when Claude Desktop reconnects.

Dispatch vs Scheduled Tasks vs remote cloud sessions

These three patterns sound similar but solve different problems:

Pattern	What it is	Desktop required?	Typical plans / notes
Remote cloud Cowork session	Default interactive Cowork session running remotely	Only for steps that need local resources	Paid plans with Cowork access; see Getting Started
Dispatch	One continuous Cowork conversation across mobile and an awake Desktop	Yes — target computer must stay awake with Desktop open	Beta for Pro and Max
Scheduled Tasks	Saved prompt that runs on a cadence	Usually no for remote runs; yes for local runs	Paid plans; remote vs local depends on configuration

Rule of thumb: Dispatch is for steering a specific awake desktop from elsewhere. Scheduled Tasks are for recurring prompts (often remote). Cloud sessions are the default interactive mode and are not the same as Dispatch.

Privacy: what “local” does and does not mean

Cloud sessions process task content on Anthropic’s infrastructure by default.
Sessions and files are saved to your Claude account—do not claim or assume they never leave the machine.
Granting a local folder does not make the whole task “on-device only”; that folder is reached through Desktop and processed as part of the session.
Check your plan, organization policy, retention terms, and model-training settings before using sensitive data. Start with Safety Tips and the Security Model.

Practical decision guide

Need only research, connectors, or account files? A cloud session (or a remote scheduled task) is usually enough.
Need a folder or app on this computer? Open Claude Desktop, grant the smallest folder or permission set, and keep the machine available for those steps.
Away from the desk but need that computer? Use Dispatch—not a pure remote session—and leave Desktop awake.
Same prompt every day or week? Prefer Scheduled Tasks; choose remote vs local based on whether the run needs on-device resources.

Frequently asked questions

Are Cowork sessions cloud or local by default?

Cloud sessions are the default and are still rolling out. Existing desktop deployments may continue to use local execution. Either way, do not treat Cowork as a guarantee that data stays only on your device.

Do my files stay on my computer?

Do not assume that. Anthropic’s Cowork guidance states that sessions and files are saved to your Claude account. Local folders are reached through Claude Desktop when you grant access and are processed as part of the task.

When must Claude Desktop stay open?

Whenever the work needs a local folder, browser, desktop app, Computer Use, Dispatch to that machine, or a local scheduled run. Remote-only steps can continue without Desktop.

Is Dispatch the same as a cloud Cowork session?

No. Dispatch links the Claude mobile app to an awake computer running Claude Desktop for one continuous conversation. A cloud session can run remote work without that awake-desktop handoff.

Can a Scheduled Task run while my computer is off?

A remote scheduled task can. A local scheduled task that needs folders or apps on the computer cannot complete those local steps until Desktop and the machine are available again.

Where should I start if I am new to Cowork?

Read What Is Claude Cowork?, then follow Getting Started. For plan eligibility, see Cowork pricing and plan access.