Can separating generator and evaluator agents reduce self-praise bias?
When agents evaluate their own work, they tend to rate it too generously. Does splitting generation from evaluation into two separate agents actually fix this problem, and how much does it improve outcomes?
Anthropic's Prithvi Rajasekaran, writing on the company's engineering blog, reports that separating the agent that produces work from the agent that judges it is "a strong lever" against a specific failure: agents asked to evaluate their own output "tend to respond by confidently praising the work—even when, to a human observer, the quality is obviously mediocre." The post states this bias "is particularly pronounced for subjective tasks like design," where there is no binary check equivalent to a verifiable software test, but adds that "even on tasks that do have verifiable outcomes, agents still sometimes exhibit poor judgment that impedes their performance."
The fix is not full elimination of leniency but a change in what is tractable to tune. Rajasekaran writes that "the separation doesn't immediately eliminate that leniency on its own; the evaluator is still an LLM that is inclined to be generous towards LLM-generated outputs." What changes is the engineering target: "tuning a standalone evaluator to be skeptical turns out to be far more tractable than making a generator critical of its own work, and once that external feedback exists, the generator has something concrete to iterate against." The design borrows its structure from Generative Adversarial Networks, pairing a generator with an evaluator in an iterative loop, with the evaluator's critique feeding back into the next generation attempt.
This frames the self-evaluation problem as a choice between two different places to put judgment: a second AI agent, or a human. Can orchestration layers make coding agents more auditable? keeps judgment and takeover points with a person and explicitly avoids adding another autonomous agent; Rajasekaran's harness goes the other way, delegating the critique itself to a dedicated AI evaluator and treating that delegation, not human oversight, as the lever against self-praise. Can language models build and maintain their own agent harnesses? argues more generally that a harness's design is separable from the model running inside it; this source is a concrete instance of that separation, in which the harness-design problem resolves into giving one agent a distinct role as skeptical judge, as built out further in Can subjective design judgment be turned into consistent grading criteria?.
The excerpt gives no measurement of how much the generator-evaluator split improves outcomes relative to self-critique, no sample size, and no comparison condition beyond Rajasekaran's own account of an earlier harness hitting "ceilings." It is a single engineer's design report on Anthropic's own blog, not an evaluated study, and the claim that a standalone evaluator is "far more tractable" to tune is asserted from experience rather than demonstrated with a controlled comparison. What follows at the strength of the evidence given is narrower: within this one build, splitting generation from evaluation was the design choice that let iteration continue past the point where asking a single agent to judge itself stalled.
Inquiring lines that read this note 2
This note is a source for these research framings, grouped by the broader line of inquiry each explores. Scan the bold lines of inquiry; follow any specific question forward.
How can model evaluations remain robust against gaming and evaluator drift? Does generative AI replace coordination with individual productivity?Related concepts in this collection 5
This note in its neighbourhood — explore the map, then jump to a related concept in the list below.
Click a node to walk · click center to open · click Open in graph to see this note in the full knowledge graph
-
Can orchestration layers make coding agents more auditable?
Does wrapping a fixed coding agent in state tracking and skill libraries improve research auditability and completeness without replacing the agent itself?
contrasts human-in-the-loop takeover points with delegating judgment to a second AI evaluator
-
Can language models build and maintain their own agent harnesses?
This explores whether an LLM's ability to create and revise its own execution infrastructure is a distinct skill from solving tasks within someone else's harness, and whether current evaluations overlook this capability.
this source is a concrete case of harness design treated as separable from the model it judges
-
Can subjective design judgment be turned into consistent grading criteria?
Can a three-agent system modeled on GANs convert vague aesthetic preferences into measurable evaluation standards? This matters because automating design critique at scale requires moving from subjective taste to verifiable criteria.
the harness this leniency fix was built inside
-
Where should an LLM judge sit in an optimization loop?
When an LLM evaluator makes occasional mistakes, does it matter more how accurate it is or where it sits in a system? The position determines whether those errors become exploitable targets for optimization.
Qualifies: a separate evaluator still gets gamed if given final authority over thousands of optimizer iterations — position in the loop matters, not separation
-
Does code LLM self-review prevent recursive training collapse?
When code models review their own generated outputs across multiple training rounds, can self-scoring or perplexity filters maintain quality, or do they eventually rubber-stamp degraded code? Understanding self-gate failure modes matters for safe recursive training.
Evidence for: self-critique (AI self-reviewing its own code) degrades into rubber-stamping over time, supporting A's case for a separate evaluator
Related papers in this collection 8
Papers most semantically related to this note, ranked by cosine similarity in the embedding space.
- Harness design for long-running application development
- Hyperagents
- When AIs Judge AIs: The Rise of Agent-as-a-Judge Evaluation for LLMs
- The Red Queen Gödel Machine: Co-Evolving Agents and Their Evaluators
- LLM Evaluators Recognize and Favor Their Own Generations
- Multi-Agent-as-Judge: Aligning LLM-Agent-Based Automated Evaluation with Multi-Dimensional Human Evaluation
- HarnessDev: Can LLMs Create and Evolve Their Own Agent Harness?
- LLM-as-a-Judge Is Not an Oracle: Why Self-Improving Agents Need Deterministic Guardrails
Original note title
separating generator and evaluator agents is a more tractable fix for self-evaluation leniency than self-critique