Scenario Authoring (Legacy)

Scenario-first authoring is a legacy workflow in the current stable SDK. New projects should use eval packs and custom inputs instead.

Recommended Path

  • Use built-in evals with khaos run <agent> --eval ...
  • Provide custom prompts via --input/--inputs
  • Customize security probes with --attacks <yaml_or_json>
Terminal
# Built-in evals
khaos evals list

# Run a focused security pass
khaos run my-agent --eval security

# Override prompts with your own cases
khaos run my-agent --eval quickstart --inputs ./tests/custom-inputs.yaml

# Add custom security attacks
khaos run my-agent --eval security --attacks ./tests/custom-attacks.yaml

If You Still Use Scenarios

The CLI still contains deprecated scenario commands for compatibility, but they are not the primary supported authoring path.

Terminal
# Legacy command group (deprecated)
khaos scenarios --help
Migration Guidance
Migrate scenario-oriented workflows to packs/evals over time. This keeps your setup aligned with the stable CLI and current documentation.

Where to Go Next