Skip to main content
Use shutdown commands deliberately: pause/hibernate preserve state for resume, while kill destroys the sandbox and releases resources.

​
Pause Or Hibernate

pause and hibernate are aliases in the CLI: 
nullspace sandbox pause sb_123
nullspace sandbox hibernate sb_123
The API snapshots the running sandbox and stops the active VM. Resume later from the returned snapshot ID: 
nullspace sandbox resume snap_123
For reusable baselines that can spawn many independent children, create an explicit snapshot: 
nullspace snapshot create sb_123
nullspace snapshot list --sandbox-id sb_123

​
Set Idle Timeout Behavior

Configure what should happen when a sandbox idles: 
nullspace sandbox timeout set sb_123 --seconds 300 --action hibernate
You can also choose timeout behavior at create time: 
nullspace sandbox create --template base --on-timeout pause --auto-resume
Use auto-resume when SDK calls or public traffic should wake the hibernated sandbox automatically.

​
Destroy A Sandbox

Destroy a sandbox when work is complete: 
nullspace sandbox kill sb_123
kill is the cleanup command used by the CLI and SDK context-manager flows. It is appropriate for disposable workspaces, one-off tests, and failed runs that do not need to be resumed.

​
Clean Up Processes First

If you only need to stop a long-running command inside a still-useful sandbox, kill the process instead: 
nullspace sandbox process list sb_123
nullspace sandbox process kill sb_123 1234