Skip to main content
A computer is where an agent does work: a disposable Linux micro-VM with a real filesystem, a shell, and an optional managed browser. It is provisioned and operated entirely by Vetta’s compute layer and wired into the durable runtime, so it pauses when the agent sleeps and resumes on the next turn — idle wall-clock time costs storage, not compute.
A fully virtualized V8-isolate mode (mode: "isolate") — near-instant boot, near-zero idle, for the lightweight majority of agent work — is coming soon. Everything on this page describes the micro-VM that ships today.
The computer — sandbox, filesystem, shell, browser, snapshots, and volumes — is available today. The vault’s sandbox-egress secret substitution is coming soon; vault injection on the MCP connector path is live. Those sections are marked inline.

​
How it maps to the turn cycle

The runtime runs one bounded harness turn, commits, and sleeps. The computer’s lifecycle is bound to that same wake/sleep cycle:
  • When the agent takes a turn, its computer is running and metered per second on the vCPU, memory, and disk it was provisioned with.
  • Between turns — waiting on a schedule, a human reply, or a long external job — the computer sleeps or is parked, and you pay for stored disk only.
  • The next exec or file operation wakes it automatically, filesystem intact.
This is the mechanism behind Vetta’s low cost on hours-long tasks: most wall-clock time is spent waiting, and waiting is nearly free. See Idle costs storage, not compute.

​
The toolset the agent gets

Inside a session the agent reaches the computer through built-in tools. Each is a governed, individually priced action, quoted against the budget before it runs.

Shell

The bash tool runs a command and returns buffered stdout, stderr, and an exit code.

Filesystem

read, write, list, mkdir, and remove over the sandbox’s disk — the canonical file API.

Browser

An optional managed browser: goto, click, type, extract, screenshot.

​
Create a computer

A computer is created with explicit resources (vCPU, memory, disk) — or an optional small/medium/large preset — and, optionally, a managed browser. There is no creation fee: you are metered per running-second while it runs, and storage-only while it sleeps. See Sandbox & lifecycle for resources and states.

​
Explore the reference

​
Configuration reference

Fields accepted by create:
​
string
required
A human-readable name, unique within the organization.
​
integer
default:"2"
Provisioned vCPU (1–16). See resources.
​
integer
default:"4096"
Provisioned memory in MiB (128–65536).
​
integer
Root disk size in whole GiB (up to 100).
​
string
Optional preset (small, medium, large) — shorthand for a vCPU/memory/disk combination.
​
string
default:"vm"
isolate coming soon (Phase 5). Execution mode. Today every computer is a micro-VM (vm); a fully virtualized isolate mode ships in Phase 5.
​
object | boolean
default:"false"
Attach a managed browser. When enabled, allowed_domains is required.
​
string
Attach a persistent volume that survives park and sleep.
​
string
Boot from a checkpoint instead of a clean image.

Next: sandbox & lifecycle

Provisioned resources, states, and how a computer is metered and torn down.