Living benchmark · 24 merged changes from Stet’s own repo, replayed by 15 AI coding setups · Updated October 21, 2026
GPT 6.1 Sol medium leads on quality vs. cost
Second of 15 on quality, 0.1 points above Opus 5. SWE-2 Max ranked first, but its cost wasn’t recorded.
- Stet score
- 65.8
- Rank 2 of 15 · Opus 5 65.7
- Average chance out of 100 of beating another setup on a task
- Cost per task
- $1.10
- 6.2× cheaper than Opus 5
- Agent time per task
- 11.8 min
- 2.0× faster than Opus 5
A directional read from 24 tasks in one repo; the top three are within 1.0 points. How this was measured
Score against cost
6 setups, from GPT 6 Luna low to GPT 6.1 Sol medium, give the best score for their cost
Compare Stet score with cost or time; the red line connects the best averages.
GPT 6.1 Sol mediumrank 2 of 15
Stet score 65.8 (56.0–75.1) · $1.10 a task · 11.8 min a task
On the line: no cheaper setup scores higher on average, and no setup reliably beats it on both score and cost.
Hover, tap or tab to another point to read it.
Standings
Setups ranked by Stet score
Stet score is a setup’s average chance, out of 100, of beating another setup on a task. Solved counts tasks whose tests passed or whose fix matched the merged change.
More metrics
- Tasks solved16/24 (13 passed, 3 judged equivalent)
- Time / task68.3 min
More metrics
- Tasks solved13/24 (10 passed, 3 judged equivalent)
- Time / task11.8 min
More metrics
- Tasks solved14/24 (12 passed, 2 judged equivalent)
- Time / task23.2 min
More metrics
- Tasks solved13/24 (11 passed, 2 judged equivalent)
- Time / task18.9 min
More metrics
- Tasks solved13/24 (12 passed, 1 judged equivalent)
- Time / task39.2 min
More metrics
- Tasks solved12/24 (9 passed, 3 judged equivalent)
- Time / task58.4 min
More metrics
- Tasks solved14/24 (11 passed, 3 judged equivalent)
- Time / task15.4 min
More metrics
- Tasks solved12/24 (8 passed, 4 judged equivalent)
- Time / task59.7 min
More metrics
- Tasks solved12/24 (11 passed, 1 judged equivalent)
- Time / task49.3 min
More metrics
- Tasks solved9/24 (8 passed, 1 judged equivalent)
- Time / task12.4 min
More metrics
- Tasks solved11/24 (7 passed, 4 judged equivalent)
- Time / task9.9 min
More metrics
- Tasks solved13/24 (11 passed, 2 judged equivalent)
- Time / task23.3 min
More metrics
- Tasks solved10/24 (8 passed, 2 judged equivalent)
- Time / task13.2 min
More metrics
- Tasks solved9/24 (9 passed, 0 judged equivalent)
- Time / task26.7 min
More metrics
- Tasks solved5/24 (5 passed, 0 judged equivalent)
- Time / task6.9 min
Task by task
SWE-2 Max solved most (16/24) · 5 unsolved
Compare two setups
Any two setups side by side on the same 24 tasks: Stet score, cost, agent time and which tasks each solved.
- GPT 6.1 Sol medium vs SWE-2 Max
- GPT 6.1 Sol medium vs Opus 5
- GPT 6.1 Sol medium vs Grok 4.7 High
- GPT 6.1 Sol medium vs Pareto 26.9
- GPT 6.1 Sol medium vs Haiku 5.5 max
- GPT 6.1 Sol medium vs GPT 6 Sol medium
- GPT 6.1 Sol medium vs GPT 6 Luna max
- GPT 6.1 Sol medium vs DeepSeek V4.1 Flash
- GPT 6.1 Sol medium vs Haiku 5.5 low+guidance
- GPT 6.1 Sol medium vs Haiku 5.5 low
- GPT 6.1 Sol medium vs Opus 4.8
- GPT 6.1 Sol medium vs Muse control
- GPT 6.1 Sol medium vs GLM 5.3 Flash
- GPT 6.1 Sol medium vs GPT 6 Luna low
See which setup wins on your repo
Stet replays your merged PRs, scores quality above pass/fail, and delivers comparison reports through your agent.
Run it on your repoHow this was measured
Each setup ran the same 24 tasks. Each task is a change merged into Stet’s repo, started from the repo as it was just before the merge. AI judges read each fix: “passed review” means an AI code reviewer approved it, and “matched the merged change” means a judge found it does what the merged change did.
Stet score is a setup’s average chance of beating another setup on a task, from 0 to 100, so 50 is even with the field. On each task the more correct fix wins: passing the tests beats matching the merged change, which beats failing. Between equally correct fixes the judges’ code-quality scores decide, and near-equal scores tie. The score’s range comes from resampling the tasks.
Cost is the coding cost each harness reported, or Stet’s estimate from recorded tokens. Agent time is how long the agent worked on a task, not end-to-end delivery time. Setups ran different test commands on some tasks, so those test results carry no weight in Stet score. The solved counts include them and are shown for reference only: tasks whose tests passed plus fixes judged equivalent to the merged change.
Setups are whole bundles: model, reasoning effort, harness and its prompts. Stet’s own read of this run is low confidence: check the evidence before rolling out any one setup. Code review didn’t cover every task, and setups recorded cost in different ways. The order above is a directional read.
Download the results (JSON)Download the summary (Markdown)
Report identity
- Generated
- Published
- Report SHA-256
0bbc1f6210cf4ed08f9a425024a6e7e45e25a003fc5fe3585536c3c694d96f46- Published version
sha256:d34123b5df1396ebc24f274af135704f492fee23dd2f05ba6770e7a6d0970661
The 24 tasks
stet-15439c21stet-232b50bastet-2450ca2dstet-3169aefastet-43493c52stet-5276aa3fstet-66762b4cstet-6f84e978stet-89dfbc27stet-b28f4fe7stet-commit-2826765estet-commit-30506f8estet-commit-342d0ac0stet-commit-5d766ddestet-commit-5e075641stet-commit-60a0e6c2stet-commit-87814583stet-commit-a8716b88stet-commit-bbbbae09stet-commit-d2ab0c25stet-commit-e41c2e2dstet-commit-e928166fstet-commit-f0caded9stet-commit-f8ae1177