Is SWE-bench Verified still meaningful?
Status:Flawed Checked against the report, 5 November 2026
Verdict
No. Its tests reject correct fixes, models have seen the answers, and labs dropped it.
Why flawed: Epoch AI rated it Flawed on 3 September 2026. In OpenAI's audit, tests reject correct fixes in 59.4% of audited tasks.[1][1] SWE-bench Verified review Epoch AI Primary
What “Flawed” meansKnown problems
- OpenAI stopped reporting it on 23 February 2026, citing contamination and flawed tests.[3][3] Why we no longer evaluate SWE-bench Verified OpenAI Vendor
- OpenAI's audit covered 27.6% of tasks. In those, 59.4% had tests that reject correct fixes.[1][1] SWE-bench Verified review Epoch AI Primary
- Every frontier model OpenAI tested could reproduce the original fixes.[1][1] SWE-bench Verified review Epoch AI Primary
- No lab headlines it in its autumn 2026 launch table.[4][4] Introducing Claude Opus 5.5 Anthropic Vendor[5][5] GPT-6 Astra benchmarks explained Vellum Secondary
- In March 2026, maintainers would merge agent pull requests at rates about 24 points below the automated scores.[6][6] Many SWE-bench-passing PRs would not merge METR Primary
- In a single-source preprint, 28.5% of 49 tasks accepted an incorrect patch. Scores ran 14.14 points higher on the hackable tasks.[7][7] Weak code verifiers on SWE-bench Verified Single source
What to look at instead
Coding moved to freshly written, partly private task sets. DeepSWE and Terminal-Bench 4.0 also carry Flawed ratings.[8][8] DeepSWE Datacurve Vendor[4][4] Introducing Claude Opus 5.5 Anthropic Vendor[9][9] Benchmark Review registry Epoch AI Primary
- DeepSWE Status:Flawed Partly. Its fresh tasks resist contamination, but Epoch AI found issues in at least 23 of 113.
- Terminal-Bench 4.0 Status:Flawed Use with care. It is a launch-table favourite, but it is rated Flawed and lab numbers disagree.
- FrontierCode Status:New / unproven Unproven. Labs headline it, but nobody has confirmed who runs it or how.
- CursorBench Status:Still useful Yes, as one signal. Remember that a product company owns it.
Where it appears in the report
Chapter 1, Benchmarks
- Figure 1. Each New Benchmark Fills Up Faster Than the Last
- Figure 5. Thirteen Flawed verdicts in ten weeks
- Table 2. First model to cross each threshold in “Go deeper: The full saturation timeline (14 benchmarks)”
- Table 4. Epoch AI Benchmark Review verdicts and the main defects found, August to October 2026 in “Go deeper: Epoch's verdicts, benchmark by benchmark”
- Table 6. Coding and software-agent benchmarks, November 2026 in “Go deeper: Coding and software-agent benchmarks (14)”
- Figure 14. OpenAI and Anthropic share only five headline benchmarks
Chapter 2, Evaluation science
- Open problems in “Go deeper: Grading: key numbers and open problems”
- Open problems in “Go deeper: Statistics: key numbers and open problems”
- Table 4. Key statistics and reliability numbers in “Go deeper: Statistics: key numbers and open problems”
- Passing a benchmark overstates real work by about two times
- Table 5. Key validity and contamination numbers in “Go deeper: Validity: key numbers and open problems”
Sources
Copied from the chapter source lists. Each number links back to the source in its chapter.
- [1] SWE-bench Verified review, Epoch AI. OpenAI's test audit and the Flawed verdict. Primary epoch.ai Chapter 1, source 5
- [2] Benchmark data bundle, Epoch AI. Dated scores (5 Nov 2026) and ceilings for most benchmarks here. Primary epoch.ai Chapter 1, source 1
- [3] Why we no longer evaluate SWE-bench Verified, OpenAI. It explains OpenAI's decision of Feb 2026. Vendor openai.com Chapter 1, source 50
- [4] Introducing Claude Opus 5.5, Anthropic. It gives Anthropic's launch table and caveats. Vendor anthropic.com Chapter 1, source 12
- [5] GPT-6 Astra benchmarks explained, Vellum. It transcribes OpenAI's launch table and discusses its framing. Secondary vellum.ai Chapter 1, source 14
- [6] Many SWE-bench-passing PRs would not merge, METR. It compares maintainer merge decisions with test results. Primary metr.org Chapter 2, source 7
- [7] Weak code verifiers on SWE-bench Verified. This single-source preprint finds hackable tests. Single source arxiv.org Chapter 2, source 37
- [8] DeepSWE, Datacurve. It describes DeepSWE and the git-history cheating it found. Vendor deepswe.datacurve.ai Chapter 1, source 52
- [9] Benchmark Review registry, Epoch AI. Lists 13 Flawed, 5 Verified and 8 unrated benchmarks in November 2026. Primary epoch.ai Chapter 1, source 3