Cloud agents run your tasks now. Your folders decide what ships
Your agent moved out of your Mac last week. Your files did not.
I wrote yesterday that review is the product once agents run for hours — one task per run, library only, screenshots before merge. On October 6 that review got a new constraint: new Cowork tasks run in the cloud, and the cloud cannot see your machine unless you set the path first.
Cloud agents now do the work away from your computer — and solo founders who ship keep one tight project folder per task, with the brief, the system, and the save rule inside it.
What changed when Cowork moved to the cloud?
Three small releases added up to one new product.
TechCrunch's report on Claude merging chat and Cowork describes the September 16 merge: one window for chat, tasks, and artifacts. Memory followed — one store shared across chat and cloud tasks. Then on October 6 new tasks started running on Anthropic servers by default.
Transparency first: I have not moved a full setup to cloud tasks yet — I am testing on side projects. The file rule is what matters. Local folders stay local. A cloud task fetches one file at a time, only through the desktop app, only while it is open. Files handed back are saved. The rest is gone when the session ends.
Here is my opinion, stated flatly: the cloud did not make agents smarter. It made your folder the brief.
Why does your folder setup decide what ships?
Because every failure I have seen this week is access, not model power.
The numbers explain the caution. SimScale surveyed 350 engineering leaders and found copilots at 67% to 76% adoption, while only about 10% deploy fully autonomous agents. SimScale CEO David Heiny said directly: "What we're seeing now is a shift from experimentation to scaled execution." Teams scale where they have governance.
The same split shows up in tooling. Bubble's roundup notes 88% of product teams use two or more AI models, with no single winner for prototyping. Anthropic's Claude Design launch notes make the same point: the team reads your codebase and design files first, then applies your colors and components after. The system carries the taste.
A cloud agent with no folder is a smart hire with a locked cabinet. It guesses. A cloud agent with a tight folder reads the same brief and components you would hand a contractor. Folders are how taste survives the move.
How do you set up folders a cloud agent can use?
You shrink the folder before the agent starts, then make saving automatic. Most tools share the Model Context Protocol for agent tool access, so your agent reaches everything you connect.
Here is the setup I use on solo builds:
- One folder per project. Brief, component set, and past decisions live there. Nothing else. Two folders means two tasks.
- Trust the parent, nothing more. Add only your projects folder in Settings. Never your home folder. Approve the project folder once per session and move on.
- A save rule in every brief. The task saves deliverables into the connected folder as it goes, in a subfolder named for the task. No folder connected means it says so at the start.
- A phone test. Start one small task, close the lid, and check it from your phone. Files in the folder means your setup held. Anything else means fix the folder first.
Run that loop once on a real task from last week. Same files in, same files out, no surprises.
When should you keep work on your own machine?
When the question is still what, or the cost of a copy is too high.
A folder that changes daily makes a bad cloud snapshot. It goes stale the day you upload it. Keep it linked through the desktop app, or sync it from GitHub or Drive where you can refresh it. Finished reference — a style guide, templates, past reports — can move to the cloud.
My rule: if work touches money, legal, or private data, or if I cannot undo it in minutes, it stays local. Code stays in my editor. Research, drafts, and plans can run in the cloud with a tight folder behind them.
The agent handles the run. You decide where the truth lives.
Frequently asked questions
Since October 6, new Cowork tasks on Pro and Max run on Anthropic servers. Old local sessions keep working, but new tasks fetch file copies through the desktop app, and anything not handed back is wiped when the session ends.
About the author
mosh
mosh is a product designer for growth, working with design thinking and ever-improving design systems. What matters: fixing conversion, whether in B2B dashboards or direct-consumer apps.
Keep reading
- Escape Ludo: game design
A covid quarantine project. Sprite design, character formation, levels, and inventory UI for a multiplayer Ludo game.
- Go Laundry: service booking platform
One platform to book cleaning services in Qatar. Art-directed brand mascots, app UI, and UX research.
- SaaS activity tracking: designing an admin log teams trust
Admins needed to see every team action in one place. Research with two managers and eight user stories turned a confusing log into filters, search, share, and export.