Models / Coding & Agentic Same model as Gemini 3 Pro in Language Models, listed again here because it’s used as a coding model and scored on that rubric. It counts once in the directory’s totals.
Maker Google
Released Feb 5, 2026 Strengths & weaknesses + Resolves 69.6% of SWE-bench Verified issues on the standard open harness + Stronger general reasoning than the Flash tier, which shows on problems that need architectural judgement − Scores below its own Flash tier on the same SWE-bench harness, so paying for Pro doesn’t buy better issue-fixing − Not served through OpenRouter, so its price and context window aren’t independently measured here
Evaluation 85% of weight measured Scored on Gemini 3 Pro · sources as of Sep 20, 2026
Confidence band 6.1–6.2 · a model inside this range isn’t meaningfully apart from this one
Code qualityw45 7.0
Rule A 69.6% resolved · 69.6% ÷ 10 · SWE-bench Verified, % resolved (mini-SWE-agent harness) (Gemini 3 Pro) · Feb 26, 2026
Web developmentw40 5.1
Rule B 1,439 rating (95% 1,430–1,447) from 13,573 votes · Scale 1,050–1,800, 0 to 10 · LMArena WebDev arena (gemini-3-pro) · Sep 11, 2026
Codebase contextw15 —
No independent measurement yet
Price & availability Measured the same way, deliberately kept out of the score: what a model costs doesn’t change what it can do.
w = weight, each criterion’s share of the overall score. Missing marks don’t count for or against. How scoring works
Highest-ROI use cases Where Gemini 3 Pro fits inside a company, ranked by the strength of published ROI evidence for each use case.
All 100 enterprise use cases → 01 IT & engineering ▸ Built for this kind of work (Coding & Agentic)02 Cross-functional operations ▸ Built for this kind of work (Coding & Agentic)
+ Excellent terminal automation, git operations, and CI/CD debugging + Far more token-efficient than reasoning-heavy rivals on routine tasks − Needs detailed, unambiguous instructions; struggles with vague requests − Smaller context window than some rivals, a constraint on huge monorepos
+ Strong at inferring intent from vague prompts and architectural context + 1M-token context supports coherent multi-file, cross-repo refactors − Can use many more tokens than leaner coding models on routine work − Narrates its reasoning at length, which slows down quick tasks
+ Open-weight performance within striking distance of proprietary leaders + Free to self-host, appealing for cost-sensitive or air-gapped teams − Requires serious infrastructure to run at full size − Tooling and IDE integrations are less mature than Copilot, Cursor, or Codex
+ Tight, real-time feedback loop; you see and steer every change + Affordable flat-rate pricing for all-day assistance − Needs a developer actively driving; not built for unattended runs − Background and async agent mode is still early and limited