A running machine saved as a named snapshot in seconds.
Save a snapshot
running when you save. The capture pauses it just long enough to grab the memory and disk together, then lets it carry on, so the machine keeps running the whole time.
snap is the short alias, so boxd snap save myapp my-workspace does the same thing.
Create machines from it
boxd machine new fresh --from-snapshot my-workspace.nyc names a snapshot in New York.
Everything running comes back
A machine created from a snapshot resumes in the state you captured. Nothing boots. A web server that was listening on the source machine is already listening on the new machine, under the same PID, with the same process start time, and the machine’s uptime continues from the source machine rather than resetting. Everything the source machine had already done stays done: dependencies installed, the database warm, the dev server compiled. That is why creating machines from a snapshot stays fast even when you make a lot of them at once. Each new machine does get its own identity when it wakes. The hostname and private IP are fresh while the processes keep going, so a long-lived process that cached the source machine’s hostname or address holds a stale value on the new machine.Automations start paused
The one exception is automations. Saving a snapshot captures the source machine’s background jobs, and every machine created from it starts them paused, the same as a fork does. Otherwise each machine created from the snapshot would run the same schedule and handle the same events as the source machine and as each other, and a team’s default snapshot would do it on every new team machine.boxd machine new --from-snapshot says how many came along, and --json carries the count as paused_automations. On the new machine, run jobs lists them, and run restart <ID> starts one there. See Forks and snapshots.
List and remove
USED is how many machines currently came from it. STATUS is ready once machines can be created from the snapshot, which takes a moment after saving.
Saving again replaces the version
Saving over a name you already used captures a new version that replaces the previous one, and--from-snapshot always uses the latest. While the new version is saving, new machines keep being created from the previous one, and once the new version is ready the name switches over to it. Older versions are cleaned up and cannot be restored or pinned. To keep an old state, save it under a new name.