2501 runner is the Benchmark driver. It dispatches scenarios as if they were real tickets, scores the result against your validation rules, and writes a report to the database. Typically only used in sandbox environments.
Subcommands
start (was run)
| Common flag | Meaning |
|---|---|
-s, --scenarios <list> | Scenario keys or tags |
-m, --mode <host|incus|lima> | Pre-provisioned hosts vs ephemeral VMs |
-g, --gateway <runner|servicenow> | Where to submit the ticket |
-i, --iter <n> | Number of iterations per scenario |
--main-engine, --secondary-engine, --specialty | Per-run overrides |
--parallel | Concurrent runs (VM modes only) |
--fail-on-error | Exit non-zero if any scenario fails |
--log-file <path> | Mirror output (ANSI-stripped) to a file |
validate
validate --runs while iterating on validation rules — much faster than re-running the agent.
flush
chaos
Drives resilience testing: runs a scenario but kills the engine at random points during execution and verifies the system recovers. Used in CI to catch regressions in restart / resume behavior.
sandbox
VM management for --mode lima or --mode incus:

