SWE-bench

SWE-bench tests whether a model can resolve real GitHub issues by generating a patch, checked by the repository's own test suite; Verified now supersedes the original set for most reporting.

Also known as: SWE-bench Full, SWE-bench Original

unassessed

This page is a discovery lead. Nobody has yet assessed it against the catalogue contract, so it carries no disposition. Absence of evidence here is not evidence of staleness.
Categorycoding
SubcategoryGitHub issue resolution / patch generation
Page statussuperseded
Metric% resolved (FAIL_TO_PASS and PASS_TO_PASS tests both pass)
Directionhigher_is_better
Unit%
Dataset size2294
Dataset licenceMIT
PublisherOriginally Princeton NLP; maintained today by the SWE-bench Team

What it measures

SWE-bench gives a model a real GitHub issue and a snapshot of the repository at the commit before it was fixed, and asks it to produce a patch that resolves the issue. Tasks require locating the relevant code across a real, multi-file Python codebase, understanding what the issue is asking for, and making a change that a project maintainer would accept, rather than answering a self-contained puzzle. The model is not shown the tests used to grade it.

Task format

Given an issue description and repository access (directly, or through retrieval, depending on the system under test), the model outputs a patch/diff. The patch is applied to a containerised checkout of the repository and graded by running two sets of tests recovered from the pull request that originally fixed the issue.

Models reporting this benchmark

No model card in ModelSpec reports this benchmark yet.

Data

This page as JSON · Edit on GitHub