Evo-Bench Findings

What nine evolvers revealed.

Every evaluated model improves the seed harness, but how it improves, where it stalls, and what it costs separate the evolvers sharply.

01 · Overview

Four results that define the benchmark

01

Every model improves the harness, but the human frontier still leads

All nine evolvers raise the Overall Score above the 29.7 CodeAct starting point, showing that harness evolution delivers gains across model families. Yet the strongest evolved result, GPT-5.6 Sol at 46.3, still trails the 47.5 human-engineered Artificial Harness.

02

Evolution saturates early, then regresses

Models find strong structures within a handful of iterations, then keep editing past the point of benefit. Opus 4.8 and GLM-5.2 achieve the highest AnytimeVal scores (51.4 / 51.0) yet freeze below their own peaks.

03

Gains are domain-shaped, and Office resists

Search rises from 11.7 to 46.5, while Office moves only a few points. On General tasks the strongest evolved harnesses reach 59.4 and surpass the human-engineered 56.3 baseline.

04

Evolved harnesses transfer across policy models

Swapping the policy to Qwen3.6-35B-A3B or GLM-5.2 preserves the gains, indicating reusable reasoning and tool-use structure rather than patches for one model's quirks.

02 · Cost and budget profiles

Models do not consistently make effective use of their full research budgets. The strongest evolvers tend to invest more steps and iterations to reach better performance, and those longer runs also incur substantially higher inference cost.

Cost vs. Overall Score. Evolver inference only, log scale. The dashed curve marks the Pareto frontier.
Budget use. Iterations, steps and wall-clock time against the 20 / 1,000 / 48h limits.
03 · Domains

Where evolution works - and where it does not

Search

11.7 → 46.5

The seed is genuinely blind

CodeAct starts with no fetch, HTML handling or result triage, so most of the gap is capability the evolver must invent.

A near-catch

Opus 4.8 reaches 46.5 against the human-engineered 46.7; GLM-5.2 and GPT-5.6 Sol follow at 45.4 and 44.5.

What gets built

Evolvers add search and fetch tools plus page cleaning that removes scripts, styles and markup noise while retaining links.

Why it rewards evolution

By adding and refining search tools, models can achieve substantially larger score gains in the Search domain.

Office

38.4 → 41.7

The stubborn domain

The best gain is +3.3 and no evolver reaches the human-engineered 43.9.

Less headroom, harder wins

The seed is already capable; remaining gains demand precise, format-aware document and spreadsheet workflows.

Sub-domain routing helps

Successful variants separate APEX evidence workflows from GDPval creation, recalculation and rendered-artifact inspection.

Human engineering still wins

Specialised office infrastructure is difficult to discover through general trial and error.

General

48.4 → 59.4

Autonomous beats hand-built

GPT-5.6 Sol and Qwen3.7-Max both reach 59.4, above the human-engineered 56.3.

Restraint is the winning move

The gain comes from removing over-steering prompt scaffolding rather than adding more instructions.

Keep the guards, drop the noise

Recovery, credential redaction and draft-email protection survive the trim.

Flexibility over specification

General tasks reward adaptable reasoning, which is the axis evolution explores most effectively.

04 · Failure Trajectories

Models struggle to explore and analyze deeply

Validation trajectories. Stars mark each run's best revision; squares mark the revision it froze.

Qwen3.6-27B: blaming noise

It reaches 49.7, crashes most tasks with a malformed verifier, repairs only to 45.4 and never restores the earlier revision.

DeepSeek V4 Pro: declaring a plateau

It hits 46.5 at iteration 3, then tunes locally and freezes at 42.6 with substantial budget unused.

Kimi K2.7 Code: disciplined but local

Kimi tests seven variants after its peak and correctly restores the byte-identical best snapshot.

The shared pattern

Models add obvious capabilities quickly, then drift into thresholds and prompt edits without paired failure analysis.

05 · Integrity

Wide diagnostic access, hard execution walls

GPT-5.6 Sol case study. The run builds a hierarchical router with domain-specific prompts and tools.

The policy never sees answers

Each rollout receives a public task view with scorer and expected fields removed, plus a fresh workspace.

Retrieval is scanned, not banned

Tool output is screened for benchmark answer keys while preserving the web access Search requires.

Semantic auditing catches evasion

All trajectories are checked for paraphrased or obfuscated leakage; affected MiniMax M3 trials are zeroed.