The cloud computer

Local agent tools chain you to a machine that has to stay awake. Buda gives every agent its own cloud computer instead — a real, isolated sandbox that keeps running, keeps your files, and works while your laptop is closed. When an agent executes, this is where it happens.

What's inside

Each cloud computer is a full working environment, not a chat sandbox:

• Files — a persistent SSD workspace (the agent's Drive) the agent reads from and writes to.
• Browser — the agent can open sites, log in, and act on the live web.
• Terminal — run commands, scripts, and tools just like a developer would.
• Git — clone, branch, commit, and push to real repositories.

You watch all of it live — every file edit, command, and page — in the agent workspace.

What makes it different

• Isolated — each agent runs in its own sandbox, so one agent's work never touches another's. This is the foundation of safe, parallel multi-agent operation.
• Long-running — work continues across hours and days; the agent doesn't lose its place when you step away.
• Persistent — files, installed tools, and Git history survive between tasks. The next session starts where the last left off.
• Sleeps when idle — an idle computer consumes no resources and wakes on demand, so you only pay for work that's actually happening.

How it fits together

Organizer (decides what runs, when, on which computer)
   ↓
Cloud computer (isolated, long-running sandbox)
   ↓
Claw — your agent — working across:
   files · browser · terminal · Git

The Organizer schedules which agent uses which computer and wakes capacity on demand. The cloud computer provides the machine; the Claw does the work inside it.

Persistence vs. session

The computer persists; a session is scoped to one task. Durable artifacts — drafts, code, datasets — live on the computer's Drive and outlast any single session, while a session only carries the short-term context of the conversation it belongs to.

Related