Discussion
0 posts
No posts in this thread yet.
benchmarks.wiki / Public workspace
Code / Agents
SWE-Bench Pro evaluates agents on long-horizon software engineering tasks in real repositories. The public card describes 731 tasks containing issue descriptions, repository identifiers, and base commits.
swe-bench-pro
Full text: eligible public problems include text, images and discussion.
Scale AI distributes SWE-Bench Pro as an evaluation of agents performing extended software engineering work in real repositories. This catalogue records publication of the Hugging Face dataset in August 2025. Its focus is repository repair over a sequence of actions, rather than isolated function completion.
The public dataset card describes 731 tasks with issue descriptions, repository identifiers and base commits. Task records also specify requirements and interfaces, placing each requested repair in a particular repository state. Evaluation uses tests that must change from failing to passing and tests that must continue to pass; matching a reference patch is not the scoring criterion.
Repository repair tasks; the import accepts problem_statement, requirements, interface, repo, base_commit, repo_language, and dockerhub_tag.
Repository patches are evaluated with fail_to_pass and pass_to_pass tests; a patch alone is not a graded result.
Requires long-horizon software engineering in real repositories.
Test success measures the behaviours exercised by the evaluation suite rather than every consequence of a repository change. Agent scaffolding, available tools, runtime environment and execution budget can affect the result as well as the underlying model. The 731 tasks described in the public card should be identified as that public collection when comparing reports, rather than assumed to represent every evaluation carrying the SWE-Bench Pro name.
1 thread and 0 posts on this page. Anyone may reply; no account is required.
Share a reproduction, report an evaluation issue, or suggest a correction to this benchmark overview.
0 posts
No posts in this thread yet.
Whole public benchmark.
Pinned source revisions, newest first:
7ab5114912baf22bb098818e604c02fe7ad2c11f · acquired 2026-09-09 · release 4cd4b68249ab7ab5114912baf22bb098818e604c02fe7ad2c11f · acquired 2026-09-09 · release 16026b211da67ab5114912baf22bb098818e604c02fe7ad2c11f · acquired 2026-09-09 · release afc4a41520ba7ab5114912baf22bb098818e604c02fe7ad2c11f · acquired 2026-09-09 · release 43e81a1c7541Scored by the benchmark’s own harness
Scored by the benchmark’s own harness
Scored by the benchmark’s own harness
Scored by the benchmark’s own harness
Scored by the benchmark’s own harness
Scored by the benchmark’s own harness
Scored by the benchmark’s own harness
Scored by the benchmark’s own harness
Scored by the benchmark’s own harness
Scored by the benchmark’s own harness
Problem identifier: instance_ansible__ansible-d58e69c82d7edd0583dd8e78d76b075c33c3151e-v173091e2e36d38c978002990795f66cfc0af30ad. No description was recorded for this problem.
Scored by the benchmark’s own harness
Scored by the benchmark’s own harness
Scored by the benchmark’s own harness
Scored by the benchmark’s own harness
Scored by the benchmark’s own harness
Scored by the benchmark’s own harness
Scored by the benchmark’s own harness
Scored by the benchmark’s own harness
Scored by the benchmark’s own harness
Scored by the benchmark’s own harness
Scored by the benchmark’s own harness
Scored by the benchmark’s own harness
Scored by the benchmark’s own harness
Scored by the benchmark’s own harness
Scored by the benchmark’s own harness
Scored by the benchmark’s own harness
Scored by the benchmark’s own harness
Scored by the benchmark’s own harness
Scored by the benchmark’s own harness
Scored by the benchmark’s own harness
Scored by the benchmark’s own harness
Problem identifier: instance_internetarchive__openlibrary-7f7e53aa4cf74a4f8549a5bcd4810c527e2f6d7e-v13642507b4fc1f8d234172bf8129942da2c2ca26. No description was recorded for this problem.
Scored by the benchmark’s own harness
Scored by the benchmark’s own harness
Scored by the benchmark’s own harness
Scored by the benchmark’s own harness
Scored by the benchmark’s own harness
Scored by the benchmark’s own harness
Scored by the benchmark’s own harness
Scored by the benchmark’s own harness
Scored by the benchmark’s own harness
Scored by the benchmark’s own harness
Scored by the benchmark’s own harness
Scored by the benchmark’s own harness
Scored by the benchmark’s own harness
Scored by the benchmark’s own harness
Problem identifier: instance_qutebrowser__qutebrowser-8f46ba3f6dc7b18375f7aa63c48a1fe461190430-v2ef375ac784985212b1805e1d0431dc8f1b3c171. No description was recorded for this problem.
Scored by the benchmark’s own harness
Scored by the benchmark’s own harness
Scored by the benchmark’s own harness
Scored by the benchmark’s own harness
Scored by the benchmark’s own harness