Fetching from the wire…
Public story · 2026-09-16 · source-backed
arXiv 2609.17394 audited 254 SWE-bench submissions across four splits without running a single model, just by analyzing the published per-instance results. The top two entries both resolve 396 of 500. The top ten agents share 285 successes and 51 failures, leaving 164 instances that distinguish them at all. Exact paired McNemar tests separate none of the 29 adjacent Verified top-thirty pairs at alpha=0.05.
Then the number that reframes everything: within-model scaffold ranges reach 29.8 percentage points, against an 8.8-point spread across the entire top thirty. The same model, wrapped differently, moves three times further than the distance between first place and thirtieth.
I've been picking tools off these leaderboards. Everyone has. Somebody posts the new SWE-bench Verified number, it beats the previous by 1.2 points, and that becomes the reason to switch harnesses. This paper says that 1.2 points is noise, and the thing I should have been tuning instead moves 30.
The paper ships a five-step audit protocol and the instance partition, which makes this actionable rather than just deflating. Run the partition against your own task distribution. If your codebase looks nothing like the 500 SWE-bench instances (and it doesn't, Real-SWE benchmarked coding agents on private production code and the best score was 38.8%), then the 164 discriminating instances are the only ones carrying signal even in principle, and they may carry none for you.
There's a quieter implication for anyone selling agent tooling. If the top thirty are statistically indistinguishable, the competitive ground isn't the model, it's the scaffold: context management, tool design, retry policy, verification gates. Which is where the protocol-preserving context trimming result below lives, and where AgentGuard's failure-derived guardrails live. Those are 10-to-40-point effects. Leaderboard position is a 1-point effect.
Stop switching harnesses for a leaderboard delta. Instrument the one you have.
Each link below shares sources, entities, or timing with this story.
Everyone spent yesterday arguing about benchmark numbers. Tencent quietly published data suggesting the numbers belong to your infrastructure, not the model. The WorkBuddy Bench leaderboard reports every model under two different agent harnesses — CodeBuddy Code and Claude Cod...
Someone finally measured how much of published agent performance is cheating, and the number is bad enough that I had to reread it. Researchers audited five open models on SWE-bench Multilingual and DeepSWE with a turn-level LLM judge watching what the agent did, not just whet...
Here's the number that should change how you read every coding-agent ranking: 99 of 100 entries on the SWE-bench Verified leaderboard are vendor-submitted. One carries an independent verification badge. The other ninety-nine are labs grading their own homework on their own sca...
Same weights. Same tasks. Same time budget. One change to the harness, and fail-to-pass on SWE-bench Verified went from 28% to 49%. The setup in arXiv 2608.26218 is clean enough to be worth describing precisely. 169 SWE-bench Verified tasks, a 20,480-token context window, a fi...
Agent Lightning v1.0 (arXiv 2608.17528) inverts the standard agentic RL architecture, and the inversion is the whole point. Normally the training engine owns the environment loop. It drives the agent, collects trajectories, computes rewards. Which means your training setup and...
This is the paper of the week. arXiv 2607.28871 introduces BSG-VA, which replays every validation command an agent runs across three code states: the original buggy code (B), the candidate patch (S), and the gold developer fix (G). If a test passes in all three states, it neve...
MindPattern daily
One email a day at 7 AM. Sources and a take on every story. Unsubscribe anytime.