Skip to main content
General

agentOS vs Sandbox

When to use the lightweight agentOS VM, a full sandbox, or both together.

  • agentOS is a lightweight VM that runs inside your process. Near-zero cold start, low memory, direct backend integration via bindings.
  • Sandboxes are full Linux environments with root access, system packages, and native binary support.
  • You can use both. agentOS works with sandboxes through sandbox mounting. Agents run in the lightweight VM by default and spin up a full sandbox on demand.

Comparison

agentOS VMFull Sandbox
CostVery low. Runs in your process.Pay per second of uptime.
StartupNear-zero cold start (~6 ms).Seconds to spin up.
Backend integrationDirect. Bindings call your functions with zero latency.Indirect. Requires network calls back to your backend.
CredentialsStay on the host. Bindings run your functions server-side; agents see only inputs and outputs.Must be injected into the sandbox environment.
PermissionsGranular, deny-by-default.Coarse-grained (container-level).
Infrastructurenpm installVendor account + API keys.
Best forCoding, file manipulation, scripting, API calls, orchestration.Browsers, desktop automation, native compilation, dev servers.

When to use each

agentOS VM

Use the lightweight VM for most agent workloads:

  • Coding and file editing
  • Running scripts and CLI tools
  • Calling APIs and services via bindings
  • Multi-agent orchestration and workflows
  • Tasks where backend integration matters (permissions, tool access, LLM routing)

Full sandbox

Spin up a sandbox when the workload needs a real Linux kernel:

  • Browsers and desktop automation (Playwright, Puppeteer, Selenium)
  • Heavy compilation and native toolchains
  • Dev servers with hot reload, databases, and system ports
  • GUI applications and VNC sessions

Both together

Use agentOS with sandbox mounting for workflows that need both:

  • Agent runs in the agentOS VM with full access to bindings and permissions
  • Sandbox spins up on demand for heavy tasks
  • Sandbox filesystem is mounted into the VM as a native directory
  • Agent reads and writes sandbox files the same way it reads local files