Guide
An agent that wrote the code is a poor judge of it: it tends to share its own blind spots. A second agent on a different model makes a better first reviewer. YOLO Studio builds that into the Background Runner as Agent review.
Get startedIn the Background Runner settings, set Agent review to Required. It is fixed onto each card when the card starts, so it applies to cards started afterwards.
When an implementation succeeds, the card stays in Doing and moves to Queued for review, then Reviewing.
The reviewer must run a different model from the one that did the work, and a different model family is preferred. If none is available, the review waits for you; a model never reviews its own work.
An approval covers exactly the commit or result it reviewed. Changes requested means nothing relies on the result until you choose Fix findings, which queues a new attempt that is reviewed again.
The card shows the verdict, the findings, the checks the reviewer ran and their limits, the exact commit or result reviewed, and why that reviewer was chosen. Review failed means the review could not run, not that the code failed it.
Agent review never merges anything. Code still lands under your chosen landing mode: manual, PR + review, or Auto merge.
An agent approval is not a pull-request review on GitHub. Any reviews your repository requires still apply.
It catches a class of mistakes early and cheaply. Read the diff of anything that matters before it ships.
Sign in with GitHub, open a workspace on your repository, and put your first agent to work in a few minutes.
Get started