Gemini 3.1 Pro vs Claude Opus 4.6: Two Weeks of Actually Using Both
When Google dropped Gemini 3.1 Pro on February 19, Reddit moved fast. A day-one review in r/google_antigravity landed within hours. The verdict was blunt: "massive, massive improvement over Gemini 3 Pro, which was a really terrible model outside benchmarks."
That's a strong opener. Because Gemini 3 Pro had decent benchmark numbers too. So something was clearly off before. And now it's supposedly fixed.
Three weeks before that, Anthropic dropped Claude Opus 4.6 on February 5. Better coding. Longer agentic tasks. A 1M context window for the first time at Opus tier. Two serious models, three weeks apart, both aimed at the same developers.
You're probably building something that needs one of them. Or you picked one already and you're wondering if you got it wrong. I know that feeling.
The problem isn't which one is "smarter." That answer changes every few weeks. The problem is cost, output limits, and what smart actually means when your code agent is stuck in a loop at 2am.
I ran both through real tasks. Agentic workflows. Long codebases. Debugging sessions that went sideways. Here's what actually happened.
Benchmarks don't tell the full story
I used to think benchmarks were mostly marketing. Then I noticed which ones actually mapped to things i do.
GPQA Diamond tests PhD-level scientific reasoning. Gemini 3.1 Pro scored 94.3%. Claude Opus 4.6 scored 91.3%. That gap matters at hard reasoning.
But on SWE-Bench Verified, the real-world software engineering test, both scored almost exactly the same. Gemini 3.1 Pro got 80.6%. Opus 4.6 got 80.8%. Basically identical.
Then there's Arena Coding. Human developers rate outputs blind. No scores. Just preference. Opus 4.6 consistently ranks first. Developers prefer the code it writes. Cleaner architecture. Better documentation. More maintainable patterns.
Gemini wins the math test. Claude writes code you actually want to maintain. Those are different things.
And at ARC-AGI-2, the abstract reasoning benchmark, Gemini 3.1 Pro scored 77.1%. That's more than double what Gemini 3 Pro managed at 31.1%. This is where the improvement is most visible.digitalapplied+1
The output limit nobody talks about
Most tutorials tell you context windows are a tie. Both models take 1M input tokens. True.
But output is different. Claude Opus 4.6 supports 128K output tokens. Gemini 3.1 Pro tops out at 64K. That's double.
That matters when you're generating full technical documentation in one call. Or writing a spec document and test suite together. Or any task where stopping halfway is annoying.
I found this the hard way. Needed a full feature spec and test suite generated together. Gemini stopped. I had to split the request. Opus did it in one pass.
One extra API call isn't the world. But it adds up across a codebase.
I spent twenty minutes trimming my prompt thinking it was too long. It wasn't the prompt. It was the output cap.
The thinking mode difference
Here's a question people always ask: do thinking modes actually help, or are they just a marketing layer?
Both models have them. Gemini 3.1 Pro has three levels: low, medium, high. You pick per request. Low for autocomplete, medium for code review, high for complex debugging.
Claude Opus 4.6 calls it Adaptive Thinking. It decides the depth automatically. You don't configure it. The model estimates.
And there's a difference in how that feels.
With Gemini, you control cost. That's genuinely useful when you're optimizing for speed at scale. With Claude, you trust it. Most of the time it's right. Sometimes it uses max reasoning on a simple task and wastes tokens.
But Claude ranked first on Terminal-Bench 2.0. It catches its own errors better. And for agentic coding, that matters. You cannot watch it work every second.
Here's what i mean: if your agent is running in the background for an hour, self-correction is worth more than any benchmark number.
Multi-step workflows: where Gemini leads
What actually happens in multi-agent, multi-file tasks surprised me.
MCP Atlas is the benchmark for this. Multi-step coding workflows across files. Gemini 3.1 Pro scored 69.2%. Claude Opus 4.6 scored 59.5%. That's not a small gap.
For complex orchestration tasks spanning multiple files and coordinated changes across a codebase, Gemini pulls ahead. This is new territory for Google. Gemini 3 Pro was weak here. 3.1 Pro is not.
But there's a flip side. Claude Opus 4.6 ranks first on the Finance Agent benchmark. Financial analysis tasks where accuracy and structured reasoning matter. No other model at the frontier touches it there.
Here's what broke my simple "pick one" logic:
Multi-step agentic coding: Gemini 3.1 Pro
Expert financial and scientific analysis: Claude Opus 4.6
Human-preferred code quality: Claude Opus 4.6
Abstract and scientific reasoning: Gemini 3.1 Proapiyi+1
The pricing math is uncomfortable
The problem here isn't what you think.
Gemini 3.1 Pro costs \(2 per million input tokens and \)12 per million output tokens. Same price as Gemini 3 Pro. Zero extra cost for a much better model.
Claude Opus 4.6 costs significantly more. Roughly 7x on input by some estimates. If you're running high-volume agentic workflows, that is not rounding error territory.
But the full picture complicates the math. Claude generates output at 107 tokens per second. Gemini runs at 66. Claude is faster. Gemini's context caching cuts costs up to 75% on repeated contexts. And Claude's Batch API gives 50% off for async workloads.nxcode+2
The actual cost depends on your workload. Don't assume cheap per-call means cheap overall.
Gemini 3.1 Pro is also in Preview. Not generally available yet. If your product has SLA requirements or depends on API stability, that's a risk worth naming.
A small thing about model naming
This has nothing to do with performance. But i have to say it.
Why do we accept this naming system? Gemini 3.1 Pro. Claude Opus 4.6. GPT-5.3-Codex. We're three letters away from router firmware.
I spent ten minutes last week trying to figure out if Gemini 3.1 Pro was different from Gemini 3.1 Pro Preview. It is, kind of. One is GA, one isn't. The names don't tell you that.
My coworker wanted to know which Gemini to use. I said 3.1 Pro. He searched "Gemini Pro" and got 1.5 Pro results. Not his fault.
Anthropic at least has a logic. Opus is hard. Sonnet is balanced. Haiku is fast. Simple. But then they released three Opus models inside six months and the clean naming started to crack.
The models are getting better. The naming is getting worse.
Who shouldn't bother with Claude Opus 4.6
Most people don't need it. Seriously.
If you're a solo developer or small team without specific use cases, the cost difference is hard to justify. Gemini 3.1 Pro leads on more benchmarks and costs a fraction of the price.
The cases where Claude Opus 4.6 is the right call are specific:
Long document generation where 128K output matters
Financial analysis or expert scientific tasks
Production workloads where GA stability is required
Agentic coding where self-correction is more important than raw throughput
And for competitive programming, Gemini 3.1 Pro reached 2887 Elo on LiveCodeBench. That's strong.
Be honest about what you're building. If it's a general coding assistant, a prototype, or internal tooling, Gemini 3.1 Pro does that well and it's cheaper. Choosing Opus 4.6 because it's the "best" model doesn't mean it's the best model for your thing.
One last thing
That Reddit day-one review called Gemini 3.1 Pro a massive improvement, then immediately reminded people how bad 3 Pro was. That context matters.
Gemini 3.1 Pro is genuinely good now. That is new. Claude Opus 4.6 was already good. That is consistent.
Which matters depends on your history with these models. Tried Gemini 3 Pro and gave up? 3.1 Pro is worth a second look. Running Opus reliably and billing it back to clients? Keep going.
The question isn't which model won the week it launched. The question is which one stops your specific problem from being a problem.
That answer is different for every codebase. And it will change again in another three weeks.
Enjoyed this article? Check out more posts.
View All Posts