Explicit opt-in
Autopilot runs only when you explicitly request it. The normal Blueprint workflow uses separate Feature or Fix and Implement commands, with human approval of the spec before code changes. Implement then follows the configured review cadence, which defaults to one review packet after the feature rather than a pause after every step.
One bounded pass
Autopilot combines Feature or Fix with Implement. It can select or resume one
feature or fix, write and critique the spec, continue through the normal
spec-approval stop, create the branch, implement small steps, run checks, and
create passing checkpoint commits. When AGENTS.md declares a Verify command,
Autopilot uses that exact shared recipe as its automated gate.
It applies qualityGates.regular from blueprint/config.json. Audit,
behavioral check, and manual try-guide automation default to manual.
Independent review defaults to when-sensitive; conditional and always
modes opt into the matching gate. When an audit runs, Autopilot
validates findings, repairs confirmed high-severity issues that stay within the
approved scope, reruns affected checks, and ends with a review packet. Broader
project cleanup remains a separate audit followed by focused fix work.
When independent review is selected, Autopilot creates an approved checkpoint after Verify, any required Check, and the verified spec. The default automatic execution setting starts an isolated reviewer and waits for its receipt. When the runtime cannot prove fresh context, exact reviewer identity and model, and completion, Blueprint preserves the request and stops with the manual fresh-session handoff. A passing independent review satisfies the configured Audit gate.
See Project Configuration for the gate modes.
Hard boundaries
Autopilot never completes, merges, pushes, deploys, publishes, sends, deletes data, runs irreversible migrations, or performs destructive actions without the separate approval required for that action.
Autopilot does not run rollback specs. Reversing completed work must use the
reviewed /rollback and /implement path so dependency and conflict gates remain
visible.
It stops when product decisions are missing, the working tree is unsafe, a required check or repair fails repeatedly, a confirmed high-severity finding cannot be fixed safely within scope, or continuing would cross one of those boundaries.
Next step
Review the final packet, diff, audit findings, and verification evidence.
Autopilot also offers a read-only walkthrough of the completed code. Run /check guide
for a manual product-review guide, then /complete when you are ready to archive
and merge.