Skip to main content
Use shutdown commands deliberately: pause/hibernate preserve state for resume, while kill destroys the machine and releases resources.

​
Pause Or Hibernate

pause and hibernate are aliases in the CLI: 
nullspace machine pause mch_123
nullspace machine hibernate mch_123
The API snapshots the running machine and stops the active VM. Resume later from the returned snapshot ID: 
nullspace machine resume snap_123
For reusable baselines that can spawn many independent children, create an explicit snapshot: 
nullspace snapshot create mch_123
nullspace snapshot list --machine-id mch_123

​
Set Idle Timeout Behavior

Configure what should happen when a machine idles: 
nullspace machine timeout set mch_123 --seconds 300 --action hibernate
You can also choose timeout behavior at create time: 
nullspace machine create --template base --on-timeout pause --auto-resume
Use auto-resume when SDK calls or public traffic should wake the hibernated machine automatically.

​
Destroy A Machine

Destroy a machine when work is complete: 
nullspace machine kill mch_123
kill is the cleanup command used by the CLI and SDK context-manager flows. It is appropriate for disposable workspaces, one-off tests, and failed runs that do not need to be resumed.

​
Clean Up Processes First

If you only need to stop a long-running command inside a still-useful machine, kill the process instead: 
nullspace machine process list mch_123
nullspace machine process kill mch_123 1234