By default, you'd be the reviewer. This project does not attempt to automate any reviews, and instead tries to make it easier for a human to review via easy access to diffs and terminal within the agent's workspace. Personally I ask the agent questions and look at the code diffs, similar to what I'd normally do in a code review.

If you wanted to be more thorough, you could scroll up in the chat and see the output of the test runs. Or to help ensure that the agent doesn't cheat, the test suite could be mounted as read-only. A custom extension could also be set up to run tests independently, and set up as a pre-review gate. However in practice (with recent models), a simple "run e2e tests" instruction in AGENTS.md would make the agent do this reliably, and I don't think I've ever seen a situation where the agent requests review without having run tests (again, with recent models). Specifying that you want to use a Test-Driven Development approach seriously goes a long way too.

Thank you, this is clear and helpful.