sandbox prepare sets up the full scenario environment (provisions VMs and runs prepare.yml to introduce the failure condition, and registers hosts and agents in the DB) but stops before dispatching the task to any agent. This lets you SSH in, inspect the state, and experiment freely.
When you’re done, sandbox restore tears everything down.
Typical Workflow
prepare, the runner prints everything you need:
sandbox prepare
| Option | Default | Description |
|---|---|---|
-s, --scenarios <list> | required | Scenarios to prepare: comma-separated tags or explicit keys. |
-m, --mode <mode> | host | Execution mode: host | incus | lima. |
-p, --scenarios-path <path> | auto-detected | Path to scenarios directory. |
--vm-templates-path <path> | auto-detected | Path to VM templates directory. |
--specialty <key> | Override specialty for all agents. | |
--env-file <path> | auto-detected | Path to env file. |
prepare.yml exits non-zero, the runner prints a warning but still finishes setting up the environment and reports it as ready, so you can SSH in and investigate why the playbook failed.
sandbox restore
Tears down environments created with sandbox prepare: destroys VMs (incus/lima), runs restore.yml (host mode), and removes registered hosts and agents from the DB.
| Option | Default | Description |
|---|---|---|
-s, --scenarios <list> | required | Scenarios to restore: comma-separated tags or explicit keys. |
-m, --mode <mode> | host | Execution mode used during prepare: host | incus | lima. |
-p, --scenarios-path <path> | auto-detected | Path to scenarios directory. |
--env-file <path> | auto-detected | Path to env file. |

