The Last Local Task: Anthropic Flips the Switch and Cowork Goes Cloud-Only for Pro and Max

Today is the day the switch flips. On October 6, 2026, every new task you hand to Claude Cowork on a Pro or Max plan runs on Anthropic’s servers, not your laptop. The “Only on your computer” toggle in Settings → General disappears from the app. The era of a consumer AI agent that does its multi-step work entirely on your own machine — reading your files, driving your browser, and writing results to your disk without a round trip to someone else’s datacenter — quietly ends for Anthropic’s mainstream paid tiers.

If that sounds dramatic, it is worth being precise about what actually changes, because a lot of what people believe about this migration is wrong. Tasks you already started on your computer keep running there until they finish, and you can download their transcripts. Nothing local gets deleted. Your cloud sessions can still read and write folders you’ve connected — provided the desktop app stays open. And Anthropic is pointing anyone who genuinely needs everything local to Claude Code in the desktop app, which still runs on your computer and keeps your folders and history there.

But the direction of travel is unmistakable, and it is bigger than one settings toggle. This is the final step of a migration Anthropic has been executing all year: Cowork launched as a separate workspace for “bigger work,” went web and mobile in July so tasks keep running after you close your laptop, merged into the main Claude chat in September as part of the “one Claude” reorganization, and now, in October, gives up local execution for its core subscription plans entirely. Each step made the agent more capable and more portable. Each step also moved the work further from the user’s own hardware.

What actually happens to your tasks

A cloud Cowork session runs in an isolated sandbox that Anthropic creates when the session starts and destroys when it ends. That sandbox reaches your computer only through the Claude desktop app, over a connection Anthropic brokers, and only for folders you have explicitly connected. In practice, the new rules break down like this:

Connected folders remain readable and writable, but only while the desktop app is open — and your computer is awake and online. Close the app or put the machine to sleep mid-task, and the bridge drops.

Local MCP servers and local connectors do not run inside the cloud session. They continue to work through the desktop app, which means their availability is tied to the same desktop-app-as-bridge requirement.

Browser use and computer use on web and mobile also need the desktop app running on your machine to act locally.

Cloud connectors — Google Drive, Gmail, and the like — plus files saved to your Claude account work with no computer at all. This is the category Anthropic clearly wants your work to live in: a report kicked off at 6 PM finishes by morning even if your laptop went to sleep, and the same session follows you from desktop to web to phone to the Chrome side panel.

The plan split matters too. The October 6 change applies to Pro and Max. Team and Enterprise owners keep control through a “Run Cowork in the cloud” administrative setting, which means organizations with data-residency obligations can still decide where the boundary sits — at least for now.

Why Anthropic is doing this

The company’s pitch is convenience, and it is not a hollow one. Scheduled tasks that run without your device being on are a genuine upgrade for solo professionals and small teams: the weekly report writes itself overnight, the pipeline review is waiting when you sit down at your desk, and nothing you start is hostage to a laptop battery. Removing the local option also simplifies a product that had grown confusing — after the September “one Claude” merge folded Cowork into ordinary chat, maintaining two entirely different execution environments for the same conversation surface was engineering overhead with diminishing returns.

There is a harder-to-avoid reading as well. Cloud execution is where the margin is. Every task that runs on Anthropic’s infrastructure is metered, observable, and upgradeable on Anthropic’s schedule — and, in a year when the company has been racing to line up compute (multi-billion-dollar datacenter deals, an IPO preparation effort that has dominated its news coverage) and iterating its privacy posture for consumer plans, keeping a fully local agent path alive for $20-a-month subscribers was an odd fit with the rest of the strategy. Local execution is difficult to meter and difficult to guarantee. Cloud execution is neither.

The Claude Code escape hatch — and its limits

Anthropic’s official answer for users who want everything on their own machine is Claude Code in the desktop app: it runs on your computer and keeps your folders and history there. For developers and technical users this is a real solution, and arguably a better tool for code-centric, repeatable work than Cowork ever was.

But it is not a like-for-like replacement, and pretending otherwise misses the point. Cowork’s audience was explicitly the non-terminal crowd — the analyst, the marketer, the small-business owner who wants to delegate a research report or a data cleanup without learning a CLI. Telling that audience to install Claude Code is telling them to change professions. The practical middle ground most guides now recommend is architectural: move shared reference files to a cloud connector or a Claude Project so tasks run even when the computer is off, connect only the folders a task genuinely needs, and keep the desktop app open when a task must touch local tools.

The quiet precedent

Strip away the product details and what remains is a precedent worth noticing. A year ago, “your AI agent runs on your machine, touches your files locally, and sends nothing to the cloud unless you ask” was a shipping consumer feature from one of the frontier labs. Today it is a deprecated option, replaced by sandboxed cloud execution with a brokered bridge back to your hardware. The security posture is arguably better audited now — ephemeral sandboxes, explicit folder connections, administrative controls — but the default has inverted. Where the default used to be “local unless you opt into the cloud,” it is now “cloud unless you’re willing to become a Claude Code user.”

Every major assistant vendor has been converging on the same answer: agents that run on infrastructure the vendor controls. OpenAI’s always-on agents, Google’s Gemini desktop integrations, and now Anthropic’s Cowork all treat the user’s device as a peripheral — a set of sensors and files the cloud agent is permitted to reach — rather than as the computer doing the thinking. Users who care about where their work executes are being sorted into a smaller and more technical niche with each product cycle.

For Pro and Max subscribers, the practical to-do list is short. Finish or note the local tasks you have running and download any transcripts you want to keep. Connect the folders Claude needs through the desktop app before starting cloud work. Move shared files to a cloud connector or Project if you want tasks to survive a closed laptop. And if anything you do truly must stay on your machine, install Claude Code now — because as of today, it is the only door Anthropic still leaves open.