GPT-6.1 Sol vs GPT-5.6 Sol
Reading a 26.2K-token pull request costs $0.1048 on GPT-5.6 Sol, 2.0× the $0.0524 it costs on GPT-6.1 Sol. Both are GPT Sol models, so the difference is one version of the same line against another. The benchmark cannot separate their recall: GPT-6.1 Sol minus GPT-5.6 Sol is +17 pts (95% interval +6 pts to +29 pts).
Side by side
| Figure | GPT-6.1 Sol | GPT-5.6 Sol |
|---|---|---|
| Price tier | Mid-range | Frontier |
| Bugs caughtshare of known bugs | 89% (better) | 72% |
| False alarmsper clean PR | 0.9 (better) | 1.2 |
| Cost per reviewmeasured | $0.0401 (better) | $0.1127 |
| Cost per bug caught | $0.0514 (better) | $0.1732 |
| Exact linecatches on the expected lines | 95% (better) | 92% |
| Review timemean | 28s (better) | 50s |
| Typical review calllist price | $0.0766 (better) | $0.1532 |
| Input / 1M tokens | $2.00 (better) | $4.00 |
| Output / 1M tokens | $10.00 (better) | $20.00 |
| Context window | 1.1M | 1.1M |
Head to head
The known bugs both were scored on, by who caught each in at least one run.
By language
| Model | All | TypeScript6 bugs | Go4 bugs | Java4 bugs | Rust4 bugs | C#3 bugs | JavaScript3 bugs | Kotlin3 bugs | PHP3 bugs | Python3 bugs | Ruby3 bugs | Swift3 bugs | C++2 bugs | C1 bug |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| GPT-6.1 Sol | 89% | 83% | 75% | 70% | 100% | 89% | 100% | 100% | 100% | 100% | 100% | 100% | 50% | 100% |
| GPT-5.6 Sol | 72% | 67% | 50% | 69% | 75% | 56% | 100% | 67% | 100% | 100% | 67% | 100% | 50% | 0% |
Of the 42 known bugs both were scored on, both caught 31 and neither caught 3. GPT-6.1 Sol caught 7 bugs that GPT-5.6 Sol missed: 1 in C, 1 in C#, 1 in Go, 1 in Kotlin, 1 in Ruby, 1 in Rust and 1 in TypeScript, most of them logic bugs. GPT-5.6 Sol caught one bug that GPT-6.1 Sol missed: 1 in Java.
On pull requests with no known bug, GPT-6.1 Sol raised 0.9 false alarms per review and GPT-5.6 Sol 1.2. A measured review cost $0.0401 on GPT-6.1 Sol, 64% less than $0.1127 on GPT-5.6 Sol.
| Pull request | Language · kind | GPT-6.1 Sol | GPT-5.6 Sol |
|---|---|---|---|
| c-ares/c-aresEvent Thread could stall when not notified of new queries on existing connections that are in a bad state | C · Resource handling | 1/1 | 0/1 |
| dotnet/orleansfix(serialization): cap codec allocations | C# · Logic | 1/1 | 0/1 |
| kotest/kotestFix DataClassEq comparator | Kotlin · Logic | 1/1 | 0/1 |
| nushell/nushellreorganize nushell configuration | Rust · Error handling | 1/1 | 0/1 |
| rails/railsReimplement Action Cable redis adapter with redis-client | Ruby · Logic | 1/1 | 0/1 |
| traefik/traefikAdd the option to define custom cipher suites for backend serversTransport | Go · API misuse | 1/1 | 0/1 |
| withastro/astroPort Go's csrf protection | TypeScript · Logic | 1/1 | 0/1 |
| jhy/jsoupStore cached child els in Attributes, not field | Java · Concurrency | 0/2 | 1/6 |
Defects caught over all runs: a PR reviewed three times with one known bug shows 3/3 when it was caught every time.
Every bug each was scored on: GPT-6.1 Sol and GPT-5.6 Sol.