Skip to main content
A scenario defines the environment used to run a measurement. The web app and current CLI use this name; older documentation may call it a run preset. A schedule controls recurring execution and sampling. Keep the task and pass criteria separate from the scenario so you can compare environments without changing what success means.

​
Choose the inputs

For private repositories, confirm that the repository is accessible through your organization’s configured repository connection before running. A private URL by itself does not grant access. For provider-key requirements, check the provider configuration in Settings and your billing workload eligibility.

​
Create and attach a scenario

The following example uses the default scaffold and the default available Claude Code model:
Copy the scenario ID and an existing eval ID into:
Review the confirmation and schedule before adding the scenario: it changes which configurations future scheduled runs use. To test an environment once without attaching it, use the quickstart’s one-off run.

​
Add a repository or tools

Use gauge repos, gauge skills, and gauge mcp to inspect available resources. gauge scenarios create --help lists the supported flags, including --repo, --ref, --skill, and --mcp. Use actual available resource IDs and versions. Launch one run and inspect its logs before expanding across many measurements. If setup fails, use Run troubleshooting.