Skip to main content
Adversarial reviews are in preview and are turned on per workspace. Ask us to enable them for yours. Until they’re on, otto.yml settings for them are read and checked, and the Otto Review check says they didn’t run.
In an adversarial review, two reviewers built on different model families review your pull request at the same time, each on its own. Otto then merges what they found into one review: one summary, one set of inline comments, one verdict. Different models miss different things. Two independent reviews catch more of them than one, and where the reviewers agree you can be more confident a finding is real.

What you see

The review looks like any other Otto review, with a few additions:
  • The summary has an Adversarial review line saying how many findings both reviewers raised and how many only one of them did.
  • Each inline finding says whether it was raised by both reviewers or by one of two. When both raised it but rated it differently (for example P1 and P3), the comment says so and keeps the more severe rating.
  • When both reviewers flag the same lines but describe the issue differently, Otto posts it once and quotes the other reviewer’s description under it.
  • The summary shows each reviewer’s own short assessment, labelled Reviewer A and Reviewer B.
How the verdict is chosen:
  • Changes requested if either reviewer found a P0 or P1.
  • Approved only if both reviewers would have approved on their own. Your approval policy still applies.
  • Otherwise, the stricter of the two reviewers’ own verdicts: if one would have requested changes on its own, the review requests changes; otherwise it comments.
The merge confidence is the lower of the two reviewers’ scores. When their scores are far apart, the summary says so. If one reviewer doesn’t finish, Otto posts the other’s review and says it is a single-model review.

Turn it on

Adversarial reviews run on full reviews: new pull requests, new commits, and /otto review. Replies to comments are answered by one reviewer, as usual. There are three modes: For the whole repository:
otto.yml
For specific paths only:
otto.yml
A path rule can also say never: files it matches never trigger an adversarial review.

Choose the reviewers

By default Otto picks a pair of reviewers from different model families for the pull request’s review depth. To choose your own, list exactly two models. Use any model id OpenRouter serves with tool use and reasoning, or one of the short names below:
otto.yml
Short names: claude-opus-5.5, claude-sonnet-5.5, claude-fable-5.1, gpt-6.1-sol, gpt-6-luna, gpt-6-astra. You can set a pair for a path too. Otto uses the first path rule in the file that sets reviewers and matches a changed file. If none does, it uses the repository’s reviewers, else its own pair. You’re billed for both reviewers at each model’s actual usage, as with any review. If a model you name isn’t available, Otto uses its own pair for that review and lists the problem on the Otto Review check.

When auto runs one

In auto mode, Otto checks four things before the review starts. If any is true, the review is adversarial: Tune them in otto.yml:
otto.yml
A path rule can turn a check off for its files or lower min_consumers. When rules disagree, the one asking for more scrutiny wins: a check the repository or another matching rule turns on stays on.

Model-assisted gate

In workspaces where it’s turned on, a small classification model also answers risky_change, breaking_contract and security_risk. It reads only the pull request’s metadata: changed file paths, sizes and risk areas, the names of changed definitions and how many files use them, and the title and description with code removed. It never sees your code or the diff.
  • It can turn on a check that Otto’s own signals left off, once its probability reaches the check’s threshold.
  • It can turn off a risky_change or breaking_contract check only when it is very sure, and only if the check rests on soft signals. It never turns off a design document, a migration with code, a path otto.yml reviews at Deep or Max, a removed definition still in use, an open blocking finding, or anything security_risk found.
  • If it’s slow or unavailable, Otto’s own signals decide.
many_consumers is always the count.
otto.yml
threshold is set for the whole repository only, not in paths.

With the change profile

In workspaces with the change profile on, the gate reads the profile instead of asking these questions separately: A threshold above those minimums still applies. A lower one has no effect: the profile is broader than the old per-check questions and would otherwise fire on most pull requests. Everything else above holds:
  • the same signals can never be turned off;
  • a check fired on soft signals is turned off only when the profile is very sure;
  • security_risk only ever adds;
  • a check that a paths rule limits to some files uses Otto’s own signals, because the profile classifies the whole pull request.

How Otto picks the mode

1

Each changed file gets a mode

The path rules that match the file: always beats auto beats never. If no rule sets one, reviews.adversarial, else your workspace’s default (auto).
2

The pull request takes the strongest

always if any file is always. Otherwise auto if any file is auto, and then Otto’s checks look only at those files. Otherwise no adversarial review. Ignored files never count.

When it stays a single review

Even when otto.yml asks for one, a review stays single, and the Otto Review check says why, when:
  • your workspace’s credit balance is low and auto-refill is off: an adversarial review costs about both reviewers’ costs together
  • Otto is already running the most adversarial reviews it allows at once, for your workspace or overall
  • your workspace has a fixed review model set by Otto’s team

Reference

Problems with these settings never stop a review. Otto ignores the invalid part, uses its defaults, and lists the problem on the Otto Review check. An invalid reviewers list is ignored as a whole, and Otto’s pair runs.