WayToClawEarn
High impactHacker News

SWE-bench Verified is saturated: OpenAI announces that this coding benchmark no longer reflects cutting-edge AI capabilities

OpenAI officially announced that SWE-bench Verified is no longer suitable for measuring cutting-edge AI coding capabilities. Top models are approaching perfect scores on this benchmark, and the community is calling for a new generation evaluation system. What does this mean for developers using AI coding tools?

WayToClawEarn EditorialPublished Apr 27, 2026Updated Aug 8, 2026

Editorial review of public sources · AI-assisted drafting. How we work · Original source

Core conclusion

On April 27, 2026, OpenAI issued an announcement announcing that the SWE-bench Verified benchmark is no longer suitable for measuring the coding capabilities of cutting-edge AI models. This news generated 298 hot comments and 165+ discussions on Hacker News. In the past two years, mainstream AI coding models have improved from 30% to nearly full scores on this benchmark, and SWE-bench's differentiation has basically disappeared. **What this means for the field of AI coding: the old era is over, and new evaluation standards are on the way. **

Key Points

  • Time of incident: April 26-27, 2026 -Affected objects: All teams and individual developers using AI coding tools
  • Core change: SWE-bench Verified is no longer a reliable indicator of differentiating cutting-edge coding models

Background and trigger events

SWE-bench is a software engineering benchmark launched by the Princeton University team to evaluate the ability of AI models to solve GitHub Issues in real code warehouses. In 2025, OpenAI partnered with Princeton to launch SWE-bench Verified as a curated subset of the benchmark.

Over the past 18 months, AI coding capabilities have experienced explosive growth:

  • End of 2024: Top models score around 40-50% on SWE-bench Verified
  • Mid-2025: Claude Code, GPT-5, etc. reach 70-80%
  • Early 2026: Frontier models generally break through 90%, and some are close to 95-98%

When all competitors are close to the ceiling, the benchmark itself naturally loses its evaluation value. OpenAI’s official blog post states that new, more challenging coding assessment frameworks are needed to continue to drive and measure the evolution of AI coding capabilities.

Key Impact

DimensionsChangeWhat it means to usRecommended actions
Evaluation criteriaSWE-bench Verified loses distinctionCannot judge model coding capabilities solely by a single benchmarkEstablish a multi-dimensional evaluation matrix and focus on the quality of actual task completion
Model selectionEach model has close to full score on the old benchmarkThe value of differentiation shifts from "who scores high" to "who performs well in actual scenarios"Prioritize testing with real projects rather than general benchmarks
Tool selectionThe actual capabilities of tools such as Claude Code / ChatGPT / Cursor vary even moreBenchmark scores increasingly do not represent actual outputPay attention to the integration and reliability of tools in actual workflows
Community directionThere is an urgent need for new benchmarksThere will be an evaluation vacuum period in the short term, and manufacturers have their own opinionsFollow up on the progress of SWE-bench 2.0 or similar new generation benchmarks

Adaptation suggestions

For AI coding tool users

  • Don’t just look at the benchmark to select tools: When all models are close to 95%, the benchmark scores have no actual reference value. You should return to real task testing: let the actual performance of Claude Code, ChatGPT, Cursor and other tools in your own project speak for itself.
  • Focus on workflow integration: The value of AI coding does not lie in a single code generation, but in the automation level of complete workflows such as PR Review, CI/CD integration, test generation, etc.
  • Establish an internal evaluation system: If your team relies on AI coding tools, it is recommended to establish its own evaluation data set (based on Issue fix tasks in the actual code base) rather than relying on third-party benchmarks.

For AI coding tool developers

  • Migrate to the new benchmark as soon as possible: If your product still uses SWE-bench Verified as the main promotional indicator, you need to start looking for or participating in a new generation of benchmark tests.
  • Emphasis on actual output indicators: Real business indicators such as user retention rate, code adoption rate, and development efficiency improvement are more convincing than benchmark scores.

Example: Custom testing framework for evaluating coding AI

python

# AI
import json
import subprocess

def evaluate_ai_coding(tool_name: str, test_cases: list[dict]) -> dict:
 """ AI """
    results = []
    for case in test_cases:
        prompt = case["prompt"]
        expected_output = case["expected"]

        actual_output = subprocess.run(
            ["claude", prompt],
            capture_output=True, text=True
        ).stdout

        results.append({
            "case": case["name"],
            "passed": evaluate_output(actual_output, expected_output),
            "execution_time": 0
        })
    return results

AI

Related extended information

Tool entry

OpenAI announced that SWE-bench Verified is no longer suitable for measuring cutting-edge coding capabilities, but OpenAI’s ChatGPT and Claude are still among the strongest coding AI tools available. It is worth noting that Claude Code performs well in practice as a coding agent, even without relying on some task types defined by SWE-bench. Open source models such as DeepSeek are also rapidly catching up on the coding circuit. Orchestration frameworks like LangGraph allow AI Agents to handle complex coding tasks more reliably.

Internal link guidance

View source →

Disclaimer: this site shares educational insights only, for inspiration and reference. No outcome guarantee; external execution and decisions are your own responsibility.