Skip to main content
A sandbox progresses through a small set of states. This guide covers each transition.

State values

The server may introduce new state values over time. The SDK wait helpers treat anything not in the lists above (except failed) as “still working”, so unknown values won’t break your code.

List sandboxes

Stop a running sandbox

waitForSandboxStop polls every 3 seconds until the sandbox enters stopped. No client-side timeout — it throws if the sandbox transitions to failed.

Start a stopped sandbox

waitForSandboxStart polls every 3 seconds until the sandbox is in one of active / running / started.

Delete a sandbox

The CLI’s --delete-volumes / --keep-volumes flags control what happens to associated volumes; the SDK call always deletes the sandbox record and the server handles cleanup.

End-to-end example

Next steps

Create a sandbox

SSH and connect

Sandbox configuration reference