Skip to main content
Manage the trail runner configs in .entire/runners/.
File-based repository Runners are separate from project Agents. To configure project Agents through the CLI, use entire api as described in Manage Agents from the CLI.
entire runner is experimental and is hidden from the top-level help. A runner scores and reviews a branch’s changes; this command manages the per-repository set: risk, confidence, drift, security, review, and others.

runner setup

Create and tailor this repository’s trail runners.
setup creates the default runner set in a repository that has none, and tailors the generic templates to this repository using gathered signal: its documentation and structure, merged pull requests and issues, checkpoint churn hotspots, and past trail findings. In a terminal with no flags, setup asks whether you want the generic defaults or defaults tailored to this repository. Otherwise, name the action up front with one of --yes, --defaults-only, --print-prompt, or --dry-run. A non-interactive run requires one of them. --yes and --dry-run each call your configured summary provider once. With no provider configured and several agents installed, you are asked which to use; --agent NAME names one for this run instead and saves nothing. Pass a runner name, such as risk or trail-risk, to tune only that runner.
--yes rewrites files in .entire/runners/. Review changes with git diff -- .entire/runners/ before committing.

Continue With

review

Run a multi-agent review against a branch.

Glossary

See how runners and trails fit together.