SWE-bench A

AI benchmark · Coding

Domains
Coding
Tier
A why
Snapshot

Open benchmark ↗github.com/swe-bench/SWE-bench

What is SWE-bench?

SWE-bench measures whether language models can resolve real-world GitHub issues by generating patches to codebases that pass tests.

Lineage

Benchmarks this one is built on and built from: versions, subsets, extensions and the indexes that combine them.

Derived benchmarks

Tier A

A

Widely used: a lab reports it, or 50 or more models are scored on it.

How much stands behind a tier: usage, who backs it, a confirmed line from its own site or paper, and a clear read on X. High with three of the four, medium with two, low otherwise.

  • no usage data
  • in curated RL directories (1 pt)
  • its family includes SWE-bench Verified (tier S)

On X · mixed, moderate buzz, from 5 posts about SWE-bench in the last month

Still widely cited for coding results, but posts focus on contamination, models searching for answers, and saturation of the Verified subset.

@nothingto12 ↗ · @kay_eth1989 ↗ · @shvgroups ↗

How we got to tier A
  1. Adoption: no usage data. Tier D.
  2. On X: mixed, moderate buzz. “Still widely cited for coding results, but posts focus on contamination, models searching for answers, and saturation of the Verified subset.” No move.
  3. In curated RL directories: 1 point, a floor of none.
  4. Root of a benchmark family that includes SWE-bench Verified (tier S): raised to A, one step below.
  5. Confirmed: a line from its own site or paper places it.

A clear view on X moves a tier one step up or down; most entries don't move. How tiers work.

Where SWE-bench sits

Its domain on the map, live. Hover a logo for its name; click to open it. Open it on the full map

The galaxy could not load. See every vendor on the board.

Next: browse all benchmarks. Entry from the RL Research daily scrape of public sources, 2026-11-05 snapshot.