Skip to content
The AI Agent Factory

Choosing where to run work

Approved by
Panaversity ·
10 min read

Match the job to the runtime

Each way of running Claude decides two things: what kind of machine the work runs on, and what survives afterward.

If you needUseWhere it runsWhat survives
Research, code or files, now, working back and forth with ClaudeA Claude chat (a cloud session in the chat examined, not confirmed for every chat)A cloud sandbox for the session. In the session examined, a Firecracker microVMThe conversation and saved files. The VM's state lasts until the VM is reclaimed or the session ends
Work on files on your own computerA chat linked to your computer, or Claude Code on your machineA cloud sandbox plus a second VM on your computer that sees only the folders you connect. Or your own machineYour files
Recurring work while your computer is offA cloud scheduled taskA new cloud session for each run, with a fresh copy of the repository and a cached setup scriptOnly external state
A stream of related tasks that outlasts one sessionA Claude project (beta, Pro and Max)Each task in its own thread, usually a new cloud session with its own sandbox. A coordinator session routes the workProject memory, instructions, the Library and pushed branches. Uncommitted sandbox changes can be lost
Recurring work on local filesA Desktop scheduled taskYour machine, while the app is open and the computer is awakeYour local folder
Repeating a check during a session/loopInside the open sessionThe session's state
Cloud sessions that must reach internal systems, or keep code on your own machinesA self-hosted environment (beta, Team and Enterprise)Your runners, inside your network. Anthropic still runs the control plane and receives the conversationCheckouts, artifacts and files on your hosts. Anthropic stores the transcript
Team work handed to Claude in SlackClaude Tag (beta, Team and Enterprise)A sandbox for each Slack thread, in an organization-level environmentThe thread, pushed branches and posted results. Files only in the sandbox are lost when the thread goes quiet
A bot, service or database that runs 24 hours a day, 7 days a weekYour own server or a managed service. Claude Code can work on it over SSHThat serverThe data that is stored durably, according to the service's design for storage and backups

The last row follows from the overview: no VM stays on for you. Work that never stops needs a service you or a provider runs.

For the project row, see Projects: coordination on top of sessions.1 For the self-hosted row, see Cloud environments and self-hosted runners.2 For the Claude Tag row, see Claude Tag.3

Inside one conversation: which of the two VMs

A conversation linked to your computer can use two VMs: the cloud workspace and the desktop workspace. Claude picks one for each step, and naming it in your request removes the guesswork.

You want toUseExample request
Rename, sort or search files in a folderThe desktop workspace"In my connected Proposals folder, rename every PDF to client and date."
Edit a CSV, Markdown or code file in placeThe desktop workspace"Fix the column headers in budget.csv in my Finance folder."
Reach a host on your office network or VPNThe desktop workspace, only with All domains allowed and no blocking device policy"From my computer, check that the staging server answers."
Build a Word, PowerPoint, Excel or PDF fileThe cloud workspace"Turn these notes into a Word file."
Look at an image or a PDF pageThe cloud workspace, after staging"Stage slide 3 of the deck and tell me what is wrong with it."
Research the web, then writeThe cloud workspace"Research AI training prices in Texas and summarize them."
Push code to GitHub or publish a packageNeither, unless All domains is allowed. Use a terminal on your own computer"Make the changes in my connected folder. I will push them."

The last row follows from the network rules for the desktop workspace.4

Five habits, whichever you choose

  1. Save anything that matters outside the VM: in an artifact, a repository, Drive, a connected app, or a folder you connected on your own computer.
  2. Expect a fresh VM after an idle gap. Have your scripts install what they need. For cloud scheduled tasks, put the installs in the environment's setup script, whose result is cached.
  3. Write scheduled prompts as complete, standalone instructions. The page on scheduled tasks explains why.
  4. Keep long-lived secrets out of the sandbox. Reach services through connectors, or use a narrow network secret. A key that can do something serious, such as paying, belongs in a connector with its own check.
  5. Enforce approval for consequential actions in the service that performs them. Consequential actions are ones with real effects, such as payments, sends and deletes. An approval prompt in Claude is an extra layer. It is not the safeguard.

The fifth habit is the same rule as in What stays your responsibility: permissions over words. The worked example shows it in a real design.

Check yourself

Question 1 / 4

0 answered

You need a bot that runs 24 hours a day. What should you use?

  1. As verified on November 9, 2026. The plan list was checked again on November 13, 2026, after the page added Ultra, and on November 16, 2026, when it listed only Pro and Max. Let Claude coordinate ongoing work with Projects, Anthropic.↑
  2. As verified on November 9, 2026. Self-hosted environments, Anthropic.↑
  3. As verified on November 9, 2026. Security and data handling, Claude Tag docs, Anthropic.↑
  4. As verified on November 16, 2026, Anthropic says registries and github.com are download-only unless the domain allowlist is set to all domains, and that to push or publish you should "use a terminal on your own computer". Network access for shell commands, Anthropic.↑
Owner
Panaversity