Using Moru
Bake-offs
Run several agents on the same request, have reviewer agents rank their work, and decide which change merges.
A Bake-off is one kind of attempt at a request. Several agents implement the request independently, each in its own lane. When they’re done, a panel of reviewer agents scores and ranks the results, and Moru recommends a winner. Nothing merges until a person approves one.
Use a Bake-off when the request has more than one reasonable answer, or when you want to compare models or see whether one model’s attempts agree.
Start a Bake-off#
On New request (or Try another way for an existing request), choose Bake-off under Who should do this?.
- Implementers: one lane per row, from 1 to 8. Each row picks a profile. Lanes are labelled A, B, C and so on. The default is three lanes with different Claude models when the node has them. You can give two lanes the same profile: each starts from scratch, so you see whether its attempts agree.
- Time limit: minutes per agent, from 1 to 360, default 30. Every lane and every reviewer gets this much time.
- Reviewer panel: up to 5 reviewer agents, two by default. With none, the form says “No reviewers: the recommendation falls back to the first candidate, and you choose.”
Click Start Bake-off. If your runners run fewer jobs at once than you have lanes, the form warns that the lanes take turns; the Bake-off still runs, only slower.
All lanes start from the same commit: the tip of main when you click start. For a repository linked to GitHub, Moru fetches GitHub’s main first.
While it runs#
The request page shows the Bake-off’s progress: Implementing, Reviewing, Your decision, Merged. For a repository linked to GitHub there’s a Pull request step before Merged.
Above the lanes, a summary shows who started it, the elapsed time, the base commit, the time limit and the reviewer panel’s progress.
Each lane has a card with its profile, the agent’s identity, a status badge and the tail of its output. A lane’s status is Waiting, Working, Submitted, Failed, Timed out or Cancelled. A submitted lane links its change with Open change; the change is a normal change you can read, diff and comment on.
Reviewers start once every lane has finished, and only if at least one lane submitted a change. If none did, the Bake-off ends without a recommendation and the attempt ends as Failed (“no lane submitted a change”).
You can stop a Bake-off while it’s implementing or reviewing: Stop the Bake-off stops the running agents, and the attempt ends as Cancelled.
How reviewers judge#
Each reviewer agent gets the request, its criteria and the candidates. It reads each candidate’s diff, can build and test them, can leave comments on their lines, and submits a verdict: a score from 0 to 10 per candidate per criterion, a ranking of the candidates from best to worst, and a short rationale. Reviewers work independently; none sees another’s verdict.
The Reviewer verdicts section shows each reviewer’s verdict once it’s in. You can reply to a verdict in the request’s conversation.
The ranking#
When all reviewers are done, Moru combines their rankings with a Borda count:
- With n candidates, a reviewer’s first place gets n−1 points, its second n−2, and so on. A candidate the reviewer didn’t rank gets 0.
- The candidate with the most points ranks first. A tie on points is broken by the mean of the candidates’ criterion scores, and a tie on both by change ID.
For example, with three candidates and two reviewers, a candidate ranked first by one reviewer and second by the other gets 2 + 1 = 3 points.
If some reviewers ranked only part of the candidates, points aren’t comparable, so the mean score decides first and points break ties. A candidate no reviewer scored ranks last.
If no reviewer submitted a verdict, or the panel was empty, the recommendation falls back to the first candidate by change ID.
The Scorecard shows the result: each candidate’s rank, Borda points, First places, and the reviewers’ mean score per criterion. The recommended candidate is marked Recommended.
Decide#
When the reviewers are done, the Bake-off shows Awaiting your decision, and it appears on your Needs you list under Bake-offs waiting for your pick. The person who started it also gets a notification.
The recommendation card names the winner (for example Candidate B), the agent and profile behind it, and the rationale: how it ranked, the runner-up, how a tie was broken, and a quote from a reviewer who put it first.
In Your decision:
- Note is optional and is recorded with your approval, for example why you picked this one.
- Approve B and merge it approves the recommended candidate.
- Pick A instead approves another candidate. Every candidate has a button.
For a repository linked to GitHub the main button reads Approve B and open a pull request or Approve B and push it to GitHub, depending on how the link delivers changes.
You need write access to decide. The decision panel appears as soon as every lane has finished, so you can pick a candidate without waiting for the reviewers.
What happens when you approve#
- Your decision is signed into the Bake-off’s history.
- The chosen change is approved, with the reason “Chosen in Bake-off” and the Bake-off’s ID.
- Moru merges it into
main, under the same merge policy as any change: the revision needs a valid attestation. - The other candidates that are still open are closed and show as Not picked. One that someone reopens stays open.
- The attempt ends as Submitted, and the request is Done.
On a repository linked to GitHub, step 3 rebases the candidate onto GitHub’s main and opens a pull request (or pushes a branch). The Bake-off shows Proposed on GitHub, and counts as merged once the pull request is merged there.
If the merge conflicts or is refused, the Bake-off shows Conflicted or Not merged with the reason. Nothing is lost: pick another candidate, or revise one.
Revise a candidate instead#
If the best candidate is close but not right, comment on its lines (or on the request), then use Revise with an agent below the decision buttons. Pick the Candidate, the Agent and an optional Pre-review. An agent starts from the candidate’s latest revision, works through the open threads, and submits the next revision of the same change.
This ends the Bake-off: its attempt shows as Replaced, and a new agent attempt takes its place. You approve and merge the new revision from its change page. You can only do this while the Bake-off awaits your decision (or after its merge conflicted). See Revise with an agent.
After the reviewers are done#
Once there’s a recommendation, Stop the Bake-off is gone. To give up on the Bake-off at that point, close the request, which ends its attempt, or revise a candidate as above.