CodePanel

Gemini 3.1 Pro vs Gemini 4 Argon

Gemini 3.1 Pro and Gemini 4 Argon charge practically the same to read a 26.2K-token pull request ($0.0524). Above 200K tokens long-context rates apply, and Gemini 4 Argon becomes the cheaper one. Both sit in the mid-range price tier, so the choice between them is about review quality more than budget. The benchmark cannot separate their recall: Gemini 3.1 Pro minus Gemini 4 Argon is −15 pts (95% interval −28 pts to −3 pts).

Side by side

Gemini 3.1 Pro and Gemini 4 Argon side by side
FigureGemini 3.1 ProGemini 4 Argon
Price tierMid-rangeMid-range
Bugs caughtshare of known bugs67%82% (better)
False alarmsper clean PR0.8 (better)1.1
Cost per reviewmeasured$0.2499$0.0527 (better)
Cost per bug caught$0.4134$0.0706 (better)
Exact linecatches on the expected lines89% (better)78%
Review timemean349s99s (better)
Typical review calllist price$0.0814$0.0766 (better)
Input / 1M tokens$2.00$2.00
Output / 1M tokens$12.00$10.00 (better)
Context window1M1M
  • Above 200K tokens, long-context rates mean Gemini 4 Argon is the cheaper of the two.
  • From 2026-12-01, after a scheduled reprice, Gemini 3.1 Pro is the cheaper of the two.

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 29Only Gemini 3.1 Pro 3Only Gemini 4 Argon 7Neither 3

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%
Gemini 4 Argon82%83%50%83%75%89%67%100%100%83%100%100%100%0%

Where they differ

Of the 42 known bugs both were scored on, both caught 29 and neither caught 3. Gemini 3.1 Pro caught 3 bugs that Gemini 4 Argon missed: 1 in C, 1 in Go and 1 in Rust. Gemini 4 Argon caught 7 bugs that Gemini 3.1 Pro missed: 1 in C++, 1 in C#, 1 in Go, 1 in JavaScript, 1 in Kotlin, 1 in PHP and 1 in TypeScript, most of them logic bugs.

On pull requests with no known bug, Gemini 3.1 Pro raised 0.8 false alarms per review and Gemini 4 Argon 1.1. A measured review cost $0.2499 on Gemini 3.1 Pro, 4.7× the cost of $0.0527 on Gemini 4 Argon.

Each known bug, and how often each model caught it
Pull requestLanguage · kindGemini 3.1 ProGemini 4 Argon
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/1
golang/gocrypto/tls: add LocalCertificate to ConnectionStateGo · Logic1/20/1
nushell/nushellreorganize nushell configurationRust · Error handling1/20/1
TanStack/queryfix(query-core): fix hydration bugs for already resolved promisesTypeScript · Logic0/11/1
dotnet/orleansfix(serialization): cap codec allocationsC# · Logic0/11/1
ggml-org/llama.cpprpc : cache and reuse compute graphsC++ · Security0/11/1
go-chi/chifeat: middleware.ClientIP, a replacement for middleware.RealIPGo · Security0/11/1
kotest/kotestFix DataClassEq comparatorKotlin · Logic0/11/1
sindresorhus/p-throttleAdd `weight` optionJavaScript · Logic0/11/1
symfony/symfony[Security] Allow multiple OIDC discovery endpointsPHP · Security0/11/1

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 Gemini 4 Argon.