guarded
Level 1
The smallest coherent change, heavily constrained by your conventions.
‹ all agents
private preview
Builder
builder
It reads the repo's own AGENT.md and conventions before writing anything, and makes the smallest coherent change that resolves the issue. The PR it opens is reviewed by your review and security agents like anyone else's — it does not get a pass for being a machine.
- Triggersa run on your own CI runner, dispatched from the dashboard
- Levelsthree, by how much autonomy the change is given
- Outputa branch and a PR, graded verified-green only when the suite proves it
- AvailabilityPrivate preview — a customer cannot switch this on yet
Its pull requests are reviewed by your other agents exactly like a human's. It does not merge, and it does not get a pass for being a machine.
Levels & categories
standard
Level 2
More latitude across files, still gated by your review agents.
verified
Level 3
Only opens the PR once the test suite proves the change green.
Sample output
The pull request it opens. Real output from a production run — not a mock-up.
fix(scan): treat a 404 from the protection endpoint as unprotected Closes #412. The check read any non-200 as "unknown", so a repository with no branch protection reported not_checked instead of a finding — the exact silent gap the epic forbids. files changed 2 (+38 −6) tests added 4 suite 186 passed grade verified-green ✓ Opened by wrokin Builder · reviewed by wrokin code-review before merge
Integration status
Private preview — not customer-enableable. There is no config stanza to commit; access is invite-only. Don’t plan an integration around it; the machine surfaces (capabilities.json) will say when that changes.