Sandbox
Sandbox provides a durable environment for running commands and working with files in a Project. Its compute can stop and resume while a persistent Sandbox keeps its home directory.
Why use Sandbox?
An agent or developer often needs a working environment across several commands or sessions. Sandbox gives that work a stable identity, with explicit controls for starting compute, preserving files, and inspecting execution history.
What you can do
- Create an environment from an OCI image and execute commands in it.
- Start, stop, or restart its compute Session.
- Inspect Sessions and create or manage Snapshots.
- Choose persistent storage or an ephemeral environment for disposable work.
Core concepts
A Sandbox is the environment that lasts until you delete it. A Session is one period of running compute. A Snapshot is a checkpoint of the persistent home directory.
Persistent Sandboxes preserve /home across Sessions. Files elsewhere are outside that persistence boundary. Ephemeral Sandboxes discard their home contents when the Session ends. Executing a command can start or resume compute when needed.
Use Sandbox
Read the CLI reference for commands or the API reference for resources, request fields, and responses.