A sandbox transitions between two long-lived states:Documentation Index
Fetch the complete documentation index at: https://docs.superserve.ai/llms.txt
Use this file to discover all available pages before exploring further.
active- VM is running, processes executing, compute billedpaused- VM paused, state persisted to disk, no compute billed
resuming while a paused sandbox is being restored to active - retry shortly. failed indicates the sandbox couldn’t boot or resume; the entry remains until you delete it. Deletion removes the sandbox entirely; further API calls return 404.
Pause
pause() checkpoints the full VM state (memory, processes, filesystem) to disk and stops billing for compute.
Resume
resume() restores a paused sandbox. Processes pick up where they left off.
sandbox.files transparently - nothing changes in your code.
Kill
kill() deletes the sandbox and all its resources. It’s idempotent - deleting an already-deleted sandbox is a no-op that swallows the 404.
Kill without an instance
In serverless contexts you often don’t have thesandbox - just the ID. Use killById / kill_by_id to delete it anyway.