exec can’t do: a managed session outlives your connection (see Sessions). Every command below uses the bonya-dev template; if you haven’t installed the CLI or logged in yet, start with the Quickstart.
1
Create a sandbox
2
Start a managed session
A simple loop stands in for any long-running process — a dev server, a queue worker, anything you’d otherwise leave running in a terminal you don’t want to keep open.
3
Attach, watch it, then detach without killing it
exec.4
Confirm it's still running from a fresh terminal
ATTACHED is now no — the session kept running after you detached.5
What suspend and resume look like
A sandbox suspends automatically after enough inactivity, and resuming is implicit the next time you reach it (see Sandboxes). This particular session won’t trigger that on its own — a detached session’s own output still counts as activity and defers idle suspend, so a
tick-every-5-seconds loop like watcher keeps the sandbox awake by design (see Sessions). A quieter detached session (or the sandbox sitting untouched entirely) would suspend on its normal schedule instead.Either way, listing sessions on a suspended sandbox doesn’t wake it — you’re served from a snapshot taken the moment it suspended, and the output says so explicitly:6
Reattach
Attaching to a suspended sandbox’s session wakes it — the process was never stopped, it just wasn’t being watched.The counter kept climbing the whole time — the same session, not a new one.
7
Kill the session
8
Clean up
Next steps
Sessions
The full attach/detach/replay model, and how the 1 MiB replay ring works.
Sandboxes
Lifecycle states, and exactly when suspend and resume happen.