Sandbox commands

Sandboxes are isolated Linux VMs. These commands cover the full lifecycle: create them, look at them, change mutable settings, pause and resume them on disk, and tear them down.

Command	Description
bhatti create	Create a new sandbox VM. Optional flags cover CPU, memory, env vars, init scripts, volumes, secrets, and file injection.
bhatti list	List your sandboxes (alias: ls). -o wide adds resource columns.
bhatti inspect	Show full details for one sandbox (alias: info) — kubectl-describe style.
bhatti edit	Toggle mutable settings. Currently only --keep-hot / --allow-cold.
bhatti stop	Snapshot to disk and free memory.
bhatti start	Resume from snapshot. Continues exactly where it left off.
bhatti destroy	Permanently destroy a sandbox (alias: rm). Volumes are detached, not deleted.

All commands accept either the sandbox name or its ID. Names are easier; IDs are stable across renames.

Quick patterns

bhatti create --name dev --cpus 2 --memory 1024
bhatti ls -o wide
bhatti inspect dev
bhatti exec dev -- npm install
bhatti stop dev                       # save state, free memory
bhatti start dev                      # resume from where it stopped
bhatti destroy dev -y

In normal operation you don’t need stop and start — idle sandboxes are paused and resumed automatically. See Thermal states for the engineering. Use them to control thermal state explicitly when you know a sandbox will be idle for a while.

See also

• Execution & shells — exec, shell, ps, ports
• Files — read/write files inside a sandbox
• Networking & sharing — publish, share
• API: POST /sandboxes