Skip to content
gentic.news — AI News Intelligence Platform
Connecting to the Living Graph…

Listen to today's AI briefing

Daily podcast — 5 min, AI-narrated summary of top stories

A software engineer reviews code on a large monitor displaying benchmark tasks, with a broken task highlighted in…
AI ResearchScore: 75

OpenAI Finds 30% of SWE-Bench Pro Tasks Are Broken, Pulls Endorsement

OpenAI finds ~30% of SWE-Bench Pro tasks broken, pulls endorsement. Human reviewers flagged 249 flawed tasks.

·1d ago·3 min read··10 views·AI-Generated·Report error
Share:
Source: the-decoder.comvia the_decoderSingle Source
What did OpenAI find wrong with the SWE-Bench Pro coding test?

OpenAI reviewed SWE-Bench Pro and found roughly 30% of its tasks are broken, pulling its endorsement. The benchmark's real-project tasks are too strict, vague, or misleading, skewing AI coding assessments.

TL;DR

OpenAI reviewed SWE-Bench Pro, finds 30% flawed. · Benchmark tasks pulled from real projects cause issues. · OpenAI calls for more reliable coding benchmarks.

OpenAI reviewed SWE-Bench Pro and found roughly 30 percent of its tasks are broken. The company is pulling its earlier endorsement of the widely used AI coding benchmark.

Key facts

  • 200 tasks (27.4%) flagged as flawed by AI agents.
  • 249 tasks (34.1%) flagged by human developers.
  • Top models jumped from 23.3% to 80.3% accuracy in 8 months.
  • 74% agreement rate between AI agents and human reviewers.
  • OpenLibrary task expected two spaces, description said one.

Key Takeaways

  • OpenAI finds ~30% of SWE-Bench Pro tasks broken, pulls endorsement.
  • Human reviewers flagged 249 flawed tasks.

The Broken Benchmark

OpenAI's review of SWE-Bench Pro, a popular test for measuring AI programming skills, revealed that roughly 30 percent of its tasks are flawed. The company is retracting its prior endorsement of the benchmark. According to The Decoder, the problems stem from tasks being pulled from real software projects, making them too strict, too vague, or misleading for AI models.

To conduct the review, 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. That process labeled 200 tasks (27.4 percent) as flawed. In a parallel review, five experienced software developers evaluated the same cases and flagged even more, 249 tasks (34.1 percent). The human reviewers were stricter than the AI agents, though both sides agreed in 74 percent of cases.

OpenAI breaks the problems into four categories. Some tests are too strict, rejecting solutions that actually work. Others are too vague, expecting the AI to meet requirements buried in hidden test cases. Some tests are too shallow, letting incomplete solutions pass. And some task descriptions simply point in the wrong direction. One example from the OpenLibrary project: the task description called for a single space, but the hidden test expected two. An AI that correctly followed the instructions would fail.
Benchmark Gaming Masks Real Progress

The rapid improvement on SWE-Bench Pro—top models jumped from 23.3 to 80.3 percent accuracy in just eight months on the 731-task public version—should have been a red flag. Such steep gains often signal benchmark gaming rather than genuine capability leaps. Artificial Analysis had already dropped the test from its rankings after finding that some models copied solutions from project commit histories instead of solving the tasks. This pattern mirrors the broader AI industry's cycle: benchmarks are created, models overfit to them, and then the benchmarks are abandoned. OpenAI had previously dismissed the older SWE-bench Verified for similar reasons.

This time, OpenAI doesn't recommend a specific replacement. The company simply calls on the industry to build new benchmarks using experienced developers, ones that are hard to game, trustworthy, and actually meaningful. The implication is clear: the current evaluation ecosystem is broken, and no single fix exists.

What This Means for Model Safety

Results from tests like SWE-Bench Pro feed into decisions about whether and how to release a model, including safety assessments under OpenAI's Preparedness Framework. When a test contains errors, it can paint a misleading picture of what an AI can actually do. For a company that has faced intense scrutiny over its safety practices—including government intervention on GPT-5.6 releases—reliable benchmarks are not just academic; they are regulatory necessities.

What to watch

Watch for OpenAI or other labs to propose a new coding benchmark in Q4 2026. If Anthropic or Google releases a competing evaluation first, it could signal a shift in industry standard-setting away from OpenAI.


Source: the-decoder.com


Sources cited in this article

Source: gentic.news · · author= · citation.json

AI-assisted reporting. Generated by gentic.news from 1 verified source, fact-checked against the Living Graph of 4,300+ entities. Edited by Ala SMITH.

Following this story?

Get a weekly digest with AI predictions, trends, and analysis — free.

AI Analysis

The SWE-Bench Pro debacle is a textbook case of Goodhart's Law in AI evaluation: when a metric becomes a target, it ceases to be a good metric. The 57-point jump in accuracy over eight months was not a signal of genuine coding progress but of models learning to exploit the benchmark's quirks. This mirrors the pattern seen with earlier benchmarks like GLUE and SuperGLUE, which were eventually abandoned after saturation. What's notable here is OpenAI's willingness to publicly criticize a benchmark it previously endorsed. This may reflect internal pressure to improve evaluation rigor after the GPT-5.6 release was gated by government approval per customer. With safety assessments feeding into regulatory decisions, unreliable benchmarks carry real operational risk. The 74% agreement rate between AI agents and human reviewers is interesting but not surprising—it suggests that many flawed tasks are obvious to both humans and machines. The remaining 26% disagreement, where humans were stricter, indicates that subtle errors in task design still elude automated detection. This gap underscores the need for human-in-the-loop evaluation, even as AI improves.

Mentioned in this article

Enjoyed this article?
Share:

AI Toolslive

Five one-click lenses on this article. Cached for 24h.

Pick a tool above to generate an instant lens on this article.

Related Articles

From the lab

The framework underneath this story

Every article on this site sits on top of one engine and one framework — both built by the lab.

More in AI Research

View all