Fetching from the wire…
Public story · 2026-07-31 · high
The best-scoring agent hit 70.0% functional correctness but scored 0.0 to 1.3 on code-structure quality, versus a 1.5 human reference.
Why now: The findings land as more teams route refactor and performance tickets to agents that are graded, so far, only on whether tests still pass.
SWE-NFI exposes a split in how AI coding agents perform: they pass functional tests but barely improve code structure, per the study behind it. The benchmark pulls 188 tasks from merged Python pull requests and grades each agent submission against 92 executable rules. That setup separates two questions most coding benchmarks blur together: did the tests still pass, and did the code actually get better.
That distinction matters for anyone routing refactoring or performance tickets to an agent. The best-performing agent in the study cleared 70.0% of functional-correctness tasks but scored only 0.0 to 1.3 on structural improvement, against a 1.5 human reference. Every agent the researchers evaluated followed the same pattern: strong on correctness, weak on structure, with none coming close to the human baseline.
A green test suite is not evidence a refactor made the code better. It proves the agent didn't break anything a test checks for, and nothing more. I'd treat that as the working rule: let agents run on behavior-changing work where tests can catch regressions. But put a human on the diff for anything labeled refactor or performance, because the tests won't tell you if the structure improved.
The gap is worth watching as more teams lean on agents for maintenance work instead of only new features. If a future version of this benchmark shows agents closing the structural-improvement gap without a corresponding drop in correctness, that changes the calculus. The 92 rules behind SWE-NFI are already doing work that code review used to do alone.
Each link below shares sources, entities, or timing with this story.
I've spent real hours tuning the CLAUDE.md in my own repos. Rewriting architecture notes. Adding conventions. Trimming when it got long. So this one stung. arXiv 2607.27250 ran a two-agent ablation across Claude Code and Codex: 17 real tasks from 3 repositories, 288 gold-test-...
VAKRA (arXiv 2608.12282) benchmarks agents against 8,000+ executable APIs across 62 domains, verifying by re-executing predicted calls against live endpoints. Accuracy falls to 50-51% on compositional APIs and degrades over 50% as depth grows. Failures concentrate in entity di...
Thinkingbox is an MCP-compatible sandbox with isolated sessions, full execution traces, and outcome evaluation against terminal backend state, carrying 507 policy-conditioned workflows across retail, hospitality, auto insurance, neobank internal IT and consulting support (arXi...
119 repository-level tasks from 98 GitHub repos across 20 scientific domains, split into issue-driven, expert-exploratory, and engineering-integration paradigms. Claude Code with Opus-5 (max) lands below 50%. arXiv The ablation is the better finding: stripping explicit scienti...
Semantics-preserving transformations of SWE-bench repos produced statistically significant degradation in 6 of 16 model-scaffold-dataset configurations. Rankings flipped by scaffold: Qwen looked robust under mini-SWE agent and brittle under OpenCode. arXiv The simpler scaffold...
This one annoyed me, because I've been running the losing pattern. SWE-QA (arXiv 2608.01507) compares the sub-agent grep pattern that Claude Code, Codex and Antigravity all ship by default against a pre-built semantic index over the same repository. Semantic search answered 65...
MindPattern daily
One email a day at 7 AM. Sources and a take on every story. Unsubscribe anytime.