Steers

Write down once what reviews should look for, then attach it to runs and Autopilot rules.

A Steer is a short document that guides reviews: what to look for and what to leave alone. It belongs to the whole organization, so you can attach it to a run or an Autopilot rule on any repository. A Steer never picks repositories or narrows what a run reads: the run's own repositories and scope apply.

Admins and Members can create and edit Steers.

What a Steer holds

  • A name and an emoji. Until you pick an emoji, V12 suggests one from the name.
  • A document in Markdown. Type @ to reference a file, folder, repository, branch, commit, pull request, finding, run, Steer or document. Drop or paste a file to attach it; a pasted link stays in the Steer. Runs read attached files, and a code review also reads the pages links point to.

Create a Steer

Open Steers and click New Steer, or press C. A card opens. In an organization without Steers, the card is on the Steers page itself.

Enter a Steer name, press Enter, and write the document.

Click Create Steer. The Steer's page opens.

Create Steer waits for a name and for every attached file to be readable. Close (×) or Esc puts the card away and keeps your draft until you reload the page. Open as a page continues the draft on a full page.

You can also create a Steer where you use it:

  • In New run, Save as Steer under What should V12 look for? turns the run's instructions into a Steer and attaches it in their place. See Review code or a change.
  • In Autopilot, Attach a Steer → New Steer… on a rule opens the card with Create and attach, which creates the Steer and attaches it to that rule. Only Admins can change rules.

Edit a Steer

Open the Steer from Steers. Its Document tab is the Steer itself. Change the name, emoji or document, and V12 saves as you write; Saving… and Saved show beside the tabs. A blank name is never saved. Until you enter one, the page shows Name the Steer to save.

A run keeps every Steer document as it was when the run started, so later edits never change a started run.

The Steer's address, /<organization>/steers/<slug>, comes from its first name and doesn't change when you rename it. The API and the CLI use the same slug.

The panel beside the document shows:

  • Autopilot: the rules the Steer is attached to; click one to open its repository's Autopilot. Admins can Add to a rule, which searches every rule the Steer is not on, or detach it with ⋯ → Detach. A rule that already carries 5 Steers shows Full.
  • Recent runs: the latest runs that carried the Steer, and All runs.
  • Findings: how many of its findings are open.
  • History: when the Steer was created.

The Findings tab lists the Steer's findings, and the Runs tab the runs that carried it. A finding counts under every Steer of the run that found it.

Archive or restore a Steer

To remove a Steer from active use, open its ⋯ menu on the Steers list or its page and choose Archive Steer…. Admins and Members can archive Steers. Archiving removes it from new run choices and detaches it from Autopilot rules. Rules keep their active or paused state and use any remaining Steers; a rule with none left uses its default review. Existing finding tags, links, and run documents stay intact, including the instructions saved by queued and running reviews.

The CLI also supports v12 steers create, edit, archive <slug> and restore <slug>. Use v12 steers list --archived to find archived documents. These writes require the opt-in steers:write scope; reads use repos:read. The REST API and MCP tools expose the same operations and preserve the same history. Restoring never reattaches old Autopilot rules.

Use Archived on the Steers list to find it again. Its document is read-only until you choose Restore Steer…. Restoring makes it available for new runs; add it back to Autopilot rules separately.

Run with a Steer

Click Run now on the Steer's page. New run opens with the Steer attached in What should V12 look for?, and in a repository workspace starts on that repository. Choose what to review, then check the price and start the run; see Approve the price.

Attach Steers to runs and rules

A run carries up to 5 Steers beside its own instructions; its page shows them, as described in Follow a run. An Autopilot rule also carries up to 5, and each run it starts carries all of them; see Attach Steers.

On this page