Papers
arxiv:2607.12227

Rethinking the Evaluation of Harness Evolution for Agents

Published on Jul 14
· Submitted by
TengXiao
on Jul 17
Authors:
,
,
,
,
,
,
,
,
,

Abstract

We revisit the evaluation of automatic harness evolution for LLM agents. Existing harness evolution methods use unit test cases to search for harness configurations and then report final performance on the same public benchmark. This protocol raises two fundamental concerns. First, harness evolution is itself an iterative search procedure that repeatedly evaluates and revises candidate harnesses using task feedback. As in agentic test-time scaling, it should therefore be compared with simple task-level search baselines under matched feedback and inference budgets to determine whether its gains arise from improved harness design or from additional search alone. Second, because the search and the final evaluation share the same benchmark, the reported gains risk overfitting to that specific task set. To address these concerns, we conduct an extensive evaluation comparing harness evolution with simple test-time scaling and discovery baselines under comparable feedback and inference budgets, and also evaluate evolved harnesses on held-out tasks to assess whether the discovered improvements generalize. Experiments on Terminal-Bench 2.1 with GPT-5.4 and Claude Opus 4.6 show that automatic harness evolution does not consistently outperform simple test-time scaling methods and exhibits limited generalization. Our results raise important questions about the effectiveness of automatic harness evolution and highlight the need for fairer evaluation protocols and benchmarks for automatic harness design. Our code is available at https://github.com/rethinking-harness-evolution.

Community

Paper submitter

In this work, we revisit how automatic harness evolution should be evaluated.

Existing automatic harness evolution methods often search over harnesses using feedback from benchmark tasks and then report final performance on the same benchmark. This makes it difficult to tell whether the gains come from genuinely better and reusable harness design, or simply from spending more inference compute, receiving repeated task feedback, and adapting to the evaluation set.

We compare harness evolution against simple test time scaling baselines under matched feedback and inference budgets. We also separately test whether evolved harnesses transfer to unseen tasks.

On Terminal Bench 2.1, harness evolution does not consistently outperform parallel sampling or sequential refinement, either with or without unit test feedback. When the search and evaluation tasks are separated, the evolved harness provides only marginal improvements on held out tasks.

Our takeaway is not that harness evolution is ineffective or unimportant. Rather, its benefits need to be assessed using fair experimental setups, strong baselines with comparable budgets, and benchmarks that are genuinely sensitive to harness design.

We hope this work encourages more careful evaluation and helps identify settings where automatic harness evolution can produce real and transferable improvements.

Sign up or log in to comment

Get this paper in your agent:

hf papers read 2607.12227
Don't have the latest CLI?
curl -LsSf https://hf.co/cli/install.sh | bash

Models citing this paper 0

No model linking this paper

Cite arxiv.org/abs/2607.12227 in a model README.md to link it from this page.

Datasets citing this paper 0

No dataset linking this paper

Cite arxiv.org/abs/2607.12227 in a dataset README.md to link it from this page.

Spaces citing this paper 0

No Space linking this paper

Cite arxiv.org/abs/2607.12227 in a Space README.md to link it from this page.

Collections including this paper 0

No Collection including this paper

Add this paper to a collection to link it from this page.