VM for Testing

sandbox create provisions a standalone VM — not tied to any specific scenario — and registers it as a host and agent in the DB. Use it when you want a persistent environment for ad-hoc tasks, manual testing, or experimenting with agent behavior outside of a scenario run.

`sandbox create`

2501-runner sandbox create --template <name> -m <mode> [options]

After creation, the runner prints SSH access details and the delete command:

Target ready: my-target
SSH:      ssh -i ~/.ssh/runner_key debian@10.0.0.7 -p 22
Agents:   agt_...
Hosts:    hst_...
Delete:   2501-runner sandbox delete -s my-target -m lima

Option	Default	Description
`--template <name>`	required	VM template to boot (e.g. `debian-docker`, `debian-k3s`).
`-m, --mode <mode>`	required	VM provider: `incus` \| `lima`.
`-n, --name <name>`	auto-generated	Name for the VM, host, and agent.
`--specialty <key>`	`SERVICES_MANAGER`	Specialty key for the registered agent.
`--vm-templates-path <path>`	auto-detected	Path to VM templates directory.
`--env-file <path>`	auto-detected	Path to env file.

`sandbox delete`

Deletes a standalone target created with sandbox create: destroys the VM and removes the host and agent from the DB.

2501-runner sandbox delete -s <name> -m <mode>

Option	Description
`-s, --name <name>`	required. Name of the target (as given at create time).
`-m, --mode <mode>`	required. VM provider: `incus` \| `lima`.
`--env-file <path>`	Path to env file (auto-detected if omitted).

Use sandbox restore (see VM from Scenario) for environments created with sandbox prepare — not sandbox delete. The runner will error if you mix them up.

Getting Started

Deployment

Core Concepts

Configure

Scenario Runner

CLI

`sandbox create`

`sandbox delete`

​sandbox create

​sandbox delete

`sandbox create`

`sandbox delete`