Using Autopilot

Autopilot is V12's continuous review workflow. Instead of creating runs by hand, you configure a repository once and let V12 keep reviewing new changes.

What Autopilot supports

For each connected repository, you can choose one of two behaviors:

• Review every push to a tracked branch.
• Review each new pull request once.

This makes Autopilot useful both for high-signal protected branches and for lighter PR-based coverage across many repositories.

Set up a repository

1. Open Autopilot.
2. Click Add repository.
3. Choose one of the repositories available through your GitHub connection and app installation.
4. Select the review behavior.
5. If you picked push-based review, choose the tracked branch.
6. Save the repository.

If the repository you need is missing, go back to GitHub installation management, grant access, then refresh the repo list.

What you see on the Autopilot page

Each configured repository shows:

• the repository name,
• the configured trigger mode,
• the tracked branch when applicable,
• whether the repository is Active or Paused,
• the Latest review, and
• Recent activity for earlier runs.

This is the fastest way to answer whether a repository is currently covered and whether new automated reviews are still landing.

Pause, edit, or remove a repository

From a repository card you can:

• toggle between Active and Paused,
• edit the trigger behavior or tracked branch, or
• remove the repository from Autopilot.

Removing a repository stops future automated reviews, but it does not delete past runs.

Manual GitHub trigger

If your GitHub integration is installed, you can also trigger a PR review from GitHub by commenting:

v12 pls audit

V12 also recognizes closely related trigger phrases such as v12 audit and v12 please review.

When to use which mode

Review every push

Choose this when:

• a branch is critical,
• changes land directly on a long-lived branch, or
• you want ongoing feedback without waiting for PR creation.

Review each new pull request once

Choose this when:

• the repository has a high PR volume,
• you want a lighter signal-to-cost ratio, or
• you mainly want an initial security pass when a PR opens.

Results

Autopilot runs still appear in the normal Runs workflow, so you can read findings, triage them, and share links exactly the same way as a manual run.