SWE B
AI benchmark · ML
- Built by
- Emulated
- On X
- @emulated_ai ↗
- Tier
- B why
- Snapshot
What is SWE?
Measures whether AI agents can deploy, debug, migrate, and maintain live production software systems across long-horizon tasks, beyond generating code patches.
Coding mostly
“80 tasks that grade not just code generation but the ability to deploy, debug, migrate, and maintain production systems”
emulated.so/software-development-automation-benchmark ↗
Who built SWE
Emulated built it
“We're introducing the **Software Development Automation Benchmark**: 80 tasks that grade not just code generation”
emulated.so/software-development-automation-benchmark ↗
Tier B
Established: 15 or more models scored, or curated RL directories rate 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.
- built by Emulated
- in curated RL directories (3 pts)
On X · mixed, high buzz, from 14 posts about SWE in the last month
SWE-bench remains the default coding benchmark cited in leaks, papers and model releases, but people raise contamination, harness-gaming and saturation concerns.
How we got to tier B
- Adoption: built by Emulated. Tier C.
- On X: mixed, high buzz. “SWE-bench remains the default coding benchmark cited in leaks, papers and model releases, but people raise contamination, harness-gaming and saturation concerns.” No move.
- In curated RL directories: 3 points, a floor of B. Raised to B.
- 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 sits
Its domain on the map, live. Hover a logo for its name; click to open it. Open it on the full map
Next: browse all benchmarks. Entry from the RL Research daily scrape of public sources, 2026-11-05 snapshot.