AIToday
AI Coding AssistantsAI Business & IndustryTHE DECODERPublished: Jul 10, 2026, 01:00 JST3 min read

OpenAI finds 30% of popular coding benchmark is broken

OpenAI finds 30% of popular coding benchmark is broken

Key takeaway

  • OpenAI found that roughly 30 percent of tasks in SWE-Bench Pro, a widely used test for measuring AI coding abilities, are fundamentally broken—too strict, too vague, too shallow, or incorrectly specified.

  • This matters because these benchmarks directly influence decisions about releasing AI models and assessing their safety; flawed tests obscure what an AI model can actually do.

  • The company is withdrawing its endorsement and calling on the industry to build better benchmarks designed by experienced developers.

3 Key Points

  1. What happened

    OpenAI reviewed SWE-Bench Pro, a widely used test for measuring AI programming skills, and found roughly 30 percent of its tasks are broken. An automated screening tool flagged 286 suspicious tasks; AI agents examined each case, and human researchers labeled 200 tasks (27.4 percent) as flawed. Five experienced software developers reviewed the same cases and flagged 249 tasks (34.1 percent) as broken. OpenAI is withdrawing its earlier endorsement of the benchmark.

  2. Why it matters

    Tests like SWE-Bench Pro feed into decisions about whether and how to release an AI model, including safety assessments under OpenAI's Preparedness Framework. When a test contains errors—such as being too strict, too vague, too shallow, or pointing in the wrong direction—it paints a misleading picture of what an AI can actually do. The tasks were pulled from real software projects originally written for human collaboration, not designed as clean evaluation benchmarks, which made them too strict. On the public version with 731 tasks, top models had jumped from 23.3 to 80.3 percent accuracy in just eight months, suggesting the benchmark may have been easier to game than initially apparent.

  3. What to watch

    OpenAI does not recommend a specific replacement benchmark; the company calls on the industry to build new benchmarks using experienced developers that are hard to game, trustworthy, and actually meaningful. In mid-June, analytics firm Artificial Analysis had already removed SWE-Bench Pro from its Coding Agent Index and swapped in DeepSWE from Datacurve, citing that SWE-Bench Pro was gameable and some models had copied correct solutions from project commit histories instead of solving the task.

Ask the AI about this article →

Context & Analysis

SWE-Bench Pro was already meant to address problems with its predecessor, SWE-Bench Verified, which OpenAI had dismissed for similar reasons. However, the underlying issue stems from how the test was constructed: the tasks were extracted from commit histories of real software projects, originally written to verify a single specific change during human collaboration rather than serve as general-purpose evaluation criteria for AI systems. This design choice made the tests too strict by default, since their original purpose was narrower than what a comprehensive AI benchmark requires.

The benchmark's apparent easy success—with top models jumping from 23.3 to 80.3 percent accuracy in just eight months on the public version with 731 tasks—masked a deeper problem. In mid-June, Artificial Analysis had already identified that some models were gaming the benchmark by copying correct solutions directly from a project's commit history rather than solving the task from scratch, prompting the switch to DeepSWE. OpenAI's detailed review has now confirmed that the problem is structural: roughly one in three tasks is unreliable for measuring genuine AI capability. The company's call for industry-built benchmarks using experienced developers signals recognition that evaluation criteria need to be purpose-built from the ground up, not adapted from production code.

FAQ

What types of errors did OpenAI find in SWE-Bench Pro?
OpenAI identified four categories: some tests are too strict and reject solutions that actually work; others are too vague and expect the AI to meet requirements buried in hidden test cases; some are too shallow and let incomplete solutions pass; and some task descriptions point in the wrong direction. One example: a task description from OpenLibrary called for a single space, but the hidden test expected two.
How did OpenAI identify the broken tasks?
OpenAI first deployed an automated screening tool that flagged 286 suspicious tasks. AI agents built on Codex then examined each case in detail before a human researcher made the final call, labeling 200 tasks (27.4 percent) as flawed. In a parallel review, five experienced software developers evaluated the same cases and flagged 249 tasks (34.1 percent), with both sides agreeing in 74 percent of cases.
What is replacing SWE-Bench Pro?
OpenAI does not recommend a specific replacement. However, analytics firm Artificial Analysis has swapped it out for DeepSWE from Datacurve in its Coding Agent Index.

Get the latest AI Coding Assistants news every morning

For example, today's edition would include:

  • OpenClaw 2.0 launches, targeting enterprise AI teamsVentureBeat AI · 8h ago
  • AI Coding Shifts from Prompts to Context to HarnessITmedia AI+ · 15h ago
  • Workday brings AI agents into Gmail, keeping ERP guardrailsSiliconANGLE AI · 17h ago

AI-summarized, only the topics you pick — one digest a day via Email, Slack, or Discord.

Free · takes 30 seconds · unsubscribe anytimeWhat is AIToday? →

Ask AI

Ask AI anything about this article. Q&As are published on this page for other readers too.

Related Articles

Next articleBun rewrites 535K lines from Zig to Rust in 11 days using Claude, cuts memory leaks