Where the work happens
- Approved by
- Panaversity ·
When a job runs on Anthropic's or OpenAI's computers, it does not use your laptop. It uses a separate, isolated computer on the company's servers, set up just for your work. Usually this is a virtual computer: a complete computer simulated in software. Think of it as a borrowed desk in someone else's office: you can work there, but it is not your own.
- Claude gives each cloud work session (one stretch of work on Anthropic's computers) its own new, temporary computer. Nobody else uses it. When the session ends, that computer is deleted. Your conversation and the files Claude saved to your account are kept. Anything else left on that computer is gone. It is a clean desk every time.1,2
- ChatGPT also runs this work on separate, protected computers. It may reuse the same computer from one task to the next, or replace it but keep the saved work, so it can pick up unfinished work later.3

Two things follow. First, the borrowed computer cannot reach your laptop by itself. Files you attach or upload are copied to the company's servers, so the work can use them after you close your laptop. Files that stay only on your laptop are used through the desktop app, while it is open. With ChatGPT, the steps that need them run on your own computer. Claude keeps a second desk for them, described below. Second, anything you want to keep must come back to you as a saved file. Do not expect it to stay on the borrowed computer.
Claude's second desk, on your own computer
In a Claude conversation, Claude can work on two separate computers, not one.1
- The cloud desk is the borrowed computer above. Claude does its heavy work there: research, building Word, Excel and PDF files, and running code. It keeps working if you close your laptop.
- The desk on your computer is a small Linux computer that the Claude desktop app runs inside your Mac or PC. It is also a virtual computer, kept apart from the rest of your machine. It sees only the folders you connect, and the changes it makes land in your real folder. It works only while the desktop app is open and online.1,4
You never log in to either desk. You ask in plain words, and Claude uses a different tool for each one.

The two desks do not share a disk. A file crosses between them only on purpose, in three steps:5
- Stage. Claude copies a file from your connected folder up to the cloud desk. The copy shows the file as it was at that moment. If you change the original later, Claude copies it again.
- Work in the cloud. Claude converts, analyzes or builds the file there.
- Commit. Claude writes the result back into your connected folder. If you changed that file in the meantime, the write is refused, so your own edit is never overwritten.
When a job only touches files in your folder, nothing is copied. Claude works on the desk on your computer, where the files already are.
| You want to | Claude uses |
|---|---|
| Rename, sort or search the files in a folder | The desk on your computer |
| Fix a spreadsheet's column names, or edit a text file in place | The desk on your computer |
| Build a Word, PowerPoint, Excel or PDF file | The cloud desk |
| Research the web, then write | The cloud desk |
| Get a finished file on your phone | The cloud desk, which hands you the file in the chat |
Claude usually picks the right desk. Naming it in your request removes the guesswork, for example: "In my connected Invoices folder, rename every PDF to the client's name and the date."
Three safety rules come with the desk on your computer:
- Only the folders you connect. Claude cannot see the rest of your computer.1
- Deleting needs your yes. Claude asks before it permanently deletes any file.4
- A limited internet. Your settings decide which websites its commands can reach. Unless you allow all websites, it can download from package sites and GitHub but not upload to them. So it cannot push code to GitHub. You do that from your own computer.6
Rule to remember: the cloud desk does the heavy work, and the desk on your computer handles your own files. Anything you want to keep must end up in a connected folder, in a file Claude hands you, or in an artifact.
Check yourself
Question 1 / 7
0 answered
When Claude works on Anthropic's computers, where does each work session run?
Sources
- As verified on November 5, 2026, Anthropic says each cloud session gets its own sandbox, "created when the session starts and destroyed when it ends", that sandboxes do not share anything, and that a Code tab cloud session left idle has its computer taken back and gets a fresh one when reopened. Anthropic does not say whether each new task inside the same conversation starts a new session. As verified on November 16, 2026, the same page says that on your computer "code execution runs in an isolated virtual machine (VM)", kept apart by Apple Virtualization on macOS or Hyper-V on Windows, that "local file access is limited to folders the member has connected on the desktop", and that "if the desktop app is offline, a session in the cloud can't reach the device". Claude Cowork architecture overview, Anthropic.↑↑2↑3↑4
- Use Claude Code in the cloud, Anthropic.↑
- As verified on November 5, 2026, OpenAI says Work's cloud tasks run in "VM-backed sandboxes" and that Work "can reuse an environment across tasks or replace it while preserving eligible state", which "doesn't mean every task receives a new container". ChatGPT Work cloud security, OpenAI.↑
- As verified on November 16, 2026, Anthropic says Claude "reaches your files, browser, and apps through the Claude Desktop app", and that Cowork "requires your explicit permission before permanently deleting any files". Use Claude Cowork safely, Anthropic.↑↑2
- Observed on November 16, 2026, in a Claude conversation linked to a Mac with one connected folder. The method and the limits seen are in the appendix. Anthropic does not publish these details, and they can change.↑
- As verified on November 16, 2026, Anthropic says that when a task runs on your computer, "Claude runs its shell commands in a virtual machine (VM)", and that on github.com, git clone, git fetch and git pull work while git push is blocked, unless the domain allowlist is set to all domains. Network access for shell commands, Anthropic.↑
- Owner
- Panaversity