What is a Sandbox?
A sandbox is an optional, isolated compute environment attached to an agent. When you configure a sandbox on an agent’s profile, Orca allocates one when a session starts, and the agent’s tools run inside it.In the dashboard, live sandbox leases are shown on the Environments page. “Sandbox” (the profile setting) and “Environment” (the dashboard surface) refer to the same thing — the concept is named Environments in the UI.
With vs. without a sandbox
If a profile has no sandbox, the agent falls back to the in-process tool set. Skills that run scripts and any shell tools require a sandbox — see Skills.
Configuration
A sandbox is described on the profile by aSandboxSpec:
Lifecycle: pause and resume
A sandbox is allocated when a session starts. When it goes idle, it can be paused rather than destroyed. A paused sandbox preserves its filesystem. Providers with a memory-suspend primitive can also preserve process memory; other providers may implement pause as stop/start, which discards memory while retaining disk. Session-scoped agent-workers account for that fallback in outbound mode: after each run they checkpoint runtime conversation state to sandbox disk, and they restore it before polling for more work after a restart. They also upload a best-effort durable copy to the runner for recovery if the sandbox itself is lost. Once the idle TTL elapses, the lease is reclaimed.Related
Environments
See and manage live sandbox leases.
Profiles
Where the sandbox is configured.
Skills
Skills that run scripts need a sandbox.