Fetching from the wire…
Public story · 2026-07-22 · high
Evolved harnesses lost to a matched-budget sampling baseline once tested on a benchmark the search never saw.
Why now: The paper posted to arXiv on July 14, 2026, arguing harness evolution keeps getting graded on the benchmark it searched against.
Evolved agent harnesses lose to simple test-time scaling once you match compute budgets, per a paper from Wang, Hajishirzi, Tsvetkov, and Dasigi. That's the control experiment self-improving agent loops keep skipping. On Terminal-Bench 2.1, harness evolution didn't consistently beat plain sampling, and the gains didn't carry to held-out tasks.
The paper, arXiv 2607.12227, flags two holes in how harness evolution gets graded. Nobody compares it to a simple baseline at matched compute. And everyone reports scores on the same public benchmark the search used to pick winners.
The fix is boring. No new tricks. Take the token budget your evolution loop spends searching harness variants. Spend the same budget on N parallel samples with a picker instead. If the evolved harness doesn't beat that baseline, you've tuned an overfit, not built a better harness.
I run agent loops that rewrite their own prompts after each cycle based on what worked. This is the control experiment I haven't run: a held-out benchmark my evolution step never sees, scored against a matched-budget baseline. The paper doesn't say if this holds past Terminal-Bench 2.1, but that's the right amount of claim for what they tested.
Each link below shares sources, entities, or timing with this story.
The system diagnoses failure traces, rewrites harness code as a patch, then keeps only changes that hold up across a batch of new failures.
HarnessRisk ran 128 sandboxed attacks across 14 model/harness setups and found configs that flagged the risk over 90% of the time still let it execute.
Sandbox memory in the test suite peaks at 28 GB a session, and latency across components swings up to 32x within the same app.
A 4,181-problem study found confidence-based escalation beats a frozen router by 4.2 points while using 37% fewer tokens.
Four model tiers spanning a 15x price gap failed at the same rate: no model buys its way out of a stale-data problem.
Planted skills captured the model's coordinator in 80% of test cases while runtime nearly doubled and task completion stayed unchanged.
MindPattern daily
One email a day at 7 AM. Sources and a take on every story. Unsubscribe anytime.