Skip to main content

Review with a second agent

Every pull request ThriveOnDev opens is reviewed in a separate run before it can be merged. Your workspace's Reviewer setting decides which agent does that review. Pick a different agent from your developer to get a second model's judgement on every change.

Why use a different reviewer​

An agent reviewing its own work tends to agree with itself. A different model notices other problems, like missed edge cases, unclear names or tests that don't test the change. Because the reviewer is a workspace setting, every pull request gets it, whichever alias implemented the task.

Set the reviewer​

  1. Open Settings → AI models.
  2. Under Reviewer, choose an alias, for example #sol if your team mostly implements with #opus.

Only owners and admins can change it. The default is Same as developer: the same agent reviews, but in a separate run with fresh context.

Make sure reviews can run​

The review runs on the AI access of the person who gave the task. If your reviewer is Codex and that person has only connected Claude, the review stops with AI access not connected. Ask the people who give tasks to add access for both agents. See Add your AI access.

What the reviewer does​

The review run reads the issue and the pull request, checks that the change does what was asked, and either approves or requests changes. Requested changes go to a fix-review run by the developer agent, and the pull request comes back to the same reviewer. See Review loop and human approval.