Documentation
Sleep, wake and what a sandbox keeps
What stays on the sandbox disk across sleep/wake, what needs restarting and what expiry or deletion removes.
Stop to sleep, start to wake
Stopping a sandbox puts it to sleep. Starting it wakes it with a fresh boot. Memory and running processes are not kept, so start your tools and servers again after waking.
What a sleeping sandbox keeps
Disk retention across stop/start has been verified in production. Sign out of AI tools before stopping if you do not want their credentials retained. Do not assume a stop signs you out. Your provider’s own session expiry still applies.
- Available now: files in /workspace stay within the sandbox lifetime.
- Available now: your home directory, including dotfiles and saved AI tool sign-ins.
- Available now: installed tools, such as apt packages and files in /usr/local, /opt and /etc.
What removes it
The lifetime timer keeps running while a sandbox sleeps. When the sandbox expires or you delete it, everything above is deleted, including the home directory and installed tools. Copy anything you need to keep before then, or put it on a persistent disk.
Billing while asleep
A sleeping sandbox stops compute charges. It keeps applicable persistent-storage charges. The sandbox's own disks are part of the sandbox and are not metered separately. Persistent disks are separate. Disk charges are currently off.