CodePanel

Gemini 3.1 Pro vs GPT-OSS 120B (Workers AI)

Reading a 26.2K-token pull request costs $0.0524 on Gemini 3.1 Pro, 5.7× the $0.0092 it costs on GPT-OSS 120B (Workers AI). Gemini 3.1 Pro is a mid-range model and GPT-OSS 120B (Workers AI) a economy one. In the benchmark Gemini 3.1 Pro caught 27 percentage points more of the known defects than GPT-OSS 120B (Workers AI) (95% interval +16 pts to +38 pts, a − b).

Side by side

Gemini 3.1 Pro and GPT-OSS 120B (Workers AI) side by side
FigureGemini 3.1 ProGPT-OSS 120B (Workers AI)
Price tierMid-rangeEconomy
Bugs caughtshare of known bugs67% (better)40%
False alarmsper clean PR0.8 (better)2.5
Cost per reviewmeasured$0.2499$0.0075 (better)
Cost per bug caught$0.4134$0.0189 (better)
Exact linecatches on the expected lines89% (better)49%
Review timemean349s55s (better)
Typical review calllist price$0.0814$0.011 (better)
Input / 1M tokens$2.00$0.35 (better)
Output / 1M tokens$12.00$0.75 (better)
Context window1M128K

Head to head

The known bugs both were scored on, by who caught each in at least one run.

Of 42 known bugs both were scored on: Both 27Only Gemini 3.1 Pro 5Only GPT-OSS 120B (Workers AI) 2Neither 8

By language

Share of known bugs each model caught, by language
ModelAllTypeScript6 bugsGo4 bugsJava4 bugsRust4 bugsC#3 bugsJavaScript3 bugsKotlin3 bugsPHP3 bugsPython3 bugsRuby3 bugsSwift3 bugsC++2 bugsC1 bug
Gemini 3.1 Pro67%67%38%78%88%56%33%67%67%67%100%100%50%50%
GPT-OSS 120B (Workers AI)40%42%13%46%71%41%11%44%33%78%33%44%33%0%

Where they differ

Of the 42 known bugs both were scored on, both caught 27 and neither caught 8. Gemini 3.1 Pro caught 5 bugs that GPT-OSS 120B (Workers AI) missed: 1 in C, 1 in Go, 1 in Ruby, 1 in Rust and 1 in Swift. GPT-OSS 120B (Workers AI) caught 2 bugs that Gemini 3.1 Pro missed: 1 in Go and 1 in TypeScript.

On pull requests with no known bug, Gemini 3.1 Pro raised 0.8 false alarms per review and GPT-OSS 120B (Workers AI) 2.5. A measured review cost $0.2499 on Gemini 3.1 Pro, 33× the cost of $0.0075 on GPT-OSS 120B (Workers AI).

Each known bug, and how often each model caught it
Pull requestLanguage · kindGemini 3.1 ProGPT-OSS 120B (Workers AI)
groue/GRDB.swiftDatabaseQueue and DatabaseSnapshot reads can access task localsSwift · Concurrency1/10/3
rails/railsReimplement Action Cable redis adapter with redis-clientRuby · Logic1/10/3
traefik/traefikAdd the option to define custom cipher suites for backend serversTransportGo · API misuse1/10/6
c-ares/c-aresEvent Thread could stall when not notified of new queries on existing connections that are in a bad stateC · Resource handling1/20/3
nushell/nushellreorganize nushell configurationRust · Error handling1/20/6
TanStack/queryfix(query-core): fix hydration bugs for already resolved promisesTypeScript · Logic0/11/6
go-gitea/giteaperf(gitdiff): optimize inline diff highlighting using cacheGo · Error handling0/11/3

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: Gemini 3.1 Pro and GPT-OSS 120B (Workers AI).