Changelog
Scheduled reviews, Steer management and zip exports
New
- Scheduled reviews. An Autopilot rule can now review a branch daily or weekly, covering either what changed since the last review or the whole branch. See Scheduled reviews.
- Archive and restore Steers. Archiving takes a Steer out of new runs and detaches it from Autopilot rules; restoring makes it available again. See Archive or restore a Steer.
- Manage Steers from the CLI, REST API and MCP. Create, edit, archive and restore Steers with
v12 steersor thecreate_steer,update_steer,archive_steerandrestore_steertools. These writes need the opt-insteers:writescope, shown as Manage Steers on an API key. See Manage Steers and the MCP tools. - Export findings as Markdown. The inbox export is now a zip with one Markdown file per finding, including its proof of concept and proposed fix, and it replaces the CSV export. Guests of a shared link can export what they see. See Export findings.
- Send feedback from an MCP client. The
send_feedbacktool reports a bug, a missing feature or a confusing result to the V12 team. See Send feedback.
Improved
- The triage controls on a finding page now also appear in a narrow window, beneath the finding title. See Triage findings.
Fixed
- Runs on Foundry projects whose
foundry.tomlsets a very large integer, such asgas_limit = 9223372036854775807, no longer fail while V12 prepares the repository.
Removed
- Dismissing findings. The Dismissed view, Dismiss from inbox and the
v12 findings dismissandrestorecommands are gone; triage by status, severity and assignee is unchanged. See Triage findings. - Finding status on public run reports. A report now lists each finding's title, severity and repository. See Public run reports.