An official change dated October 6, 2026 says new Cowork tasks for Pro and Max run in the cloud, while tasks already started on a device continue under their existing execution method (official Cowork usage guidance). That does not mean you can turn off every Mac: keep a desktop path available when a task needs a connected local folder or a tool served by a local MCP process.
Fast decision: classify each task by where its files and tools live; keep the Mac available only for workflows that still depend on local access.
This is for Pro or Max users checking where new and existing tasks run; administrators reviewing folder and tool permissions; and developers deciding whether a local or cloud Agent workflow fits their environment.
Last updated October 9, 2026. The plan and task behavior below was checked against Anthropic’s Cowork help guidance, architecture overview, and safety documentation.
Does Claude Cowork cloud work in 2026 mean your Mac can stay off?
Often, yes—for a task that runs in the cloud and uses resources available to that cloud session. Not necessarily, if the job needs a folder on your Mac or a locally hosted tool. The important distinction is between where the Agent executes and how it gets access to a resource. Cloud execution changes the first; it does not automatically make every local resource available from the cloud.
| Workflow option | Where the Agent runs | What must be available | Best fit |
|---|---|---|---|
| Cloud-only task | Cloud | Files and tools the cloud session can access | Tasks that do not need a Mac-local folder or local service |
| Cloud task with a desktop connection | Cloud, with access mediated by the desktop setup | The relevant desktop app and authorized folder connection, when required | Work that needs selected local files but can use the supported connection |
| Local task or local-tool workflow | On the device or through its local environment | The Mac, local files, and any required local services | Tasks tied to local applications, data, or MCP servers |
The official change is specifically described for new Cowork tasks on Pro and Max. Do not extend that statement to Team, Enterprise, every Cowork feature, or every organization’s policy. The official Team and Enterprise Cowork administration guidance is the place to check plan-specific controls. If you administer a managed account, verify the policy that applies to your organization instead of treating an individual plan’s behavior as a guarantee.
The practical upside of cloud execution is that the Mac does not have to perform the Agent’s work for a cloud-native task. The trade-off is that you need to verify access paths and permissions rather than assume the cloud session inherits everything from a desktop session.
Decision point: if the task can finish with its cloud-accessible files and tools while the Mac is disconnected, you usually do not need to keep that Mac awake just to run the Agent. Test this with a non-sensitive task before changing a production workflow.
How do cloud tasks access Claude Cowork local files?
A cloud task does not get blanket access to the files on your Mac merely because you use Cowork on that Mac. In a desktop-connected workflow, access depends on the folders you connect and the desktop path that makes those files available. Treat the selected folder as a boundary: check its scope, contents, and permissions before you start a task.
The official Cowork architecture overview explains the distinction between cloud sessions and local access paths. The engineering explanation of Cowork’s isolation and file permissions provides additional context on how the environment limits access. Neither source is a reason to assume that every file on a device is uploaded, accessible, or retained for a particular length of time. For retention, use the official data-storage policy; do not promise a deletion schedule to colleagues unless that policy explicitly supports it.
| File or access situation | What to check | Decision |
|---|---|---|
| File is available to the cloud session | Confirm it is in the task’s supported access path and that sharing is allowed | Run without relying on the Mac as a file bridge |
| File is inside a connected local folder | Confirm the folder is authorized and the desktop connection is available when the workflow needs it | Keep the desktop path available for that task |
| File is elsewhere on the Mac | Do not assume Cowork can browse it automatically | Move or connect only the required material through an approved route |
| File is confidential or regulated | Review folder scope, account policy, and handling requirements before connecting it | Ask the administrator to approve the access path first |
This is where “cloud” can be misunderstood. A cloud-running Agent and a cloud-accessible copy of every local file are not the same thing. If your workflow depends on a connected folder, test what happens when the desktop app is closed or the Mac is offline. That tells you whether the workflow is truly cloud-only or still relies on a local bridge.
For a small team, a useful scenario is a developer asking Cowork to summarize a project folder and prepare a change report. If that folder is reachable only through a desktop connection, the task may still depend on the Mac being available even though the Agent itself runs in the cloud. If the report uses files already accessible to the cloud session, that desktop dependency may disappear. Make the test with a copy of the project data, not with your only production copy.
When reviewing sensitive material, follow the product’s safe-use recommendations. In particular, confirm that the connected folder contains only the data the task needs. Narrow folder scope is easier to review than a broad connection that exposes unrelated files.
Can Claude Cowork local MCP servers follow a cloud session?
Do not assume they can. A local MCP server runs in an environment you control; a cloud session does not automatically acquire a network route to a process on your Mac. The architecture documentation distinguishes local integrations from remote MCP connections. If a tool must be available without the Mac, determine whether it has a supported remote connection rather than treating the local server as a cloud-hosted component.
The official guidance for custom remote MCP connectors describes the remote connector route. That is a different setup from simply leaving a local MCP process installed on a desktop. For each plugin or tool, record its server location, authentication method, required network path, and whether it needs a local application or file system.
A practical test is simple: disconnect the Mac from the workflow and run a low-risk task that calls the same tool. If the call fails, the dependency is not cloud-independent. If it succeeds, document which remote connector and permissions made it possible. Avoid concluding that a tool works remotely just because its name appears in both desktop and cloud interfaces.
Check these failure points before moving a team workflow:
- The MCP server binds only to a local interface and is not reachable by the cloud service.
- Credentials are stored in the desktop environment and are not available to the remote connection.
- The tool reads local paths, application state, or files outside the connected folder.
- A network or organization policy blocks the route required by a remote connector.
- The team has not approved the broader access that a remote service may need.
The advantage of a local MCP setup is proximity to local tools and data. Its disadvantage is operational dependence: the Mac, process, credentials, and network path may all need attention. A remote connector can remove some of that device dependence, but it introduces a separate configuration and permission review. Choose based on where the tool needs to run, not on the assumption that “MCP” means one universal connection model.
Will an existing local Cowork task move to the cloud?
No automatic migration should be assumed. The official change notice says tasks already started on a device continue under the execution method they were using; it does not say that an active local task silently changes into a cloud task. Check the task’s current status and execution context before closing the app, disconnecting the Mac, or starting a replacement task.
This matters when a task has partially processed local files or called local tools. Recreating it in the cloud may not reproduce the same file access or tool state. Before you stop the original, save any needed output, note the inputs and connected folders, and confirm that the new execution path can reach the same dependencies. The help guidance is the source for the task behavior; your own test should confirm the state of your particular job.
A migration check you can complete before changing the workflow
Use this sequence for a personal setup or a controlled team pilot. Do not use a production folder or privileged tool as the first test.
- Record the task state. Identify which jobs started locally and which are new cloud tasks. Confirm whether an existing job is still running before closing the desktop app.
- Map the data. List the files the task reads and writes. Mark each as cloud-accessible, inside a connected folder, or local-only. Do not include unrelated folders “just in case.”
- Inventory MCP dependencies. For each tool, note whether its server is local or remote, what it can access, and where its credentials are held. A local server is not cloud-ready by default.
- Test desktop availability. With a disposable task, close or disconnect the desktop path and observe whether the work continues. If it stops accessing a folder or tool, retain that dependency in the workflow plan.
- Review permissions with the administrator. On a managed account, confirm plan scope, connector approval, folder policy, and any device requirements. Do not apply Pro or Max behavior to Team or Enterprise without checking the applicable controls.
- Run a least-access pilot. Grant access only to the files and tools needed for one representative task. Compare the result with the existing local workflow before moving more users.
- Document the rollback. Keep the former execution route available until the new one has completed the task and produced the required output. Record who can restore access if the cloud path fails.
For scheduled Cowork work, check the official recurring-task guidance rather than assuming a schedule has the same access conditions as an interactive session. A scheduled task still needs its inputs and tools to be reachable in the environment where it runs. If a recurring job depends on a local folder or local MCP process, verify that dependency separately before removing the Mac from the schedule.
Keep, remove, or replace the local path
Keep the Mac path if the task reads files that are available only through a connected local folder, calls a local MCP server, or depends on a desktop application. You may not need to keep it continuously available if the task runs only after someone opens the desktop connection; the exact requirement depends on the connection behavior you verify.
Remove the Mac from the execution path when the task can access its required files and tools without the device, and a disconnected test completes successfully. That can eliminate a device that was being kept online solely to run an Agent. It does not remove the need to maintain permissions, review outputs, or provide an approved route to source data.
Choose a remote connector or another approved service when the tool needs to be reachable independently of a single Mac and your administrator accepts the access model. This can make a workflow less dependent on one desktop, but it does not make the tool configuration or security review disappear.
If your organization needs a persistent macOS environment for local software, a local MCP process, or repeatable testing, a remote Mac can preserve that execution path without assigning a desk machine to every task. Review the Mac rental use cases to see whether your workload fits that model. For a hands-on trial, compare the actual connection and access requirements with the available Mac mini rental option; confirm availability and delivery details directly rather than assuming a specific configuration.
For a Cowork workflow that is already fully cloud-based, keeping a Mac powered on just in case adds maintenance, device-management work, and an unnecessary dependency. For one that still needs local folders or tools, relying on a developer’s personal desktop creates availability and permission risks. If the Mac environment is needed only for temporary testing or a bounded project, Kvmzen’s Mac rental options give you a way to evaluate a Mac-based path without treating permanent ownership as the default. If you have no local dependency, you do not need to rent or leave a Mac running for Cowork’s new cloud tasks.