← Back to Blog

Gemini 4 Argon: Google's New Frontier Model, Tested

Published: November 2026 | Category: AI Engineering

Gemini 4 Argon overview

Google's first Gemini 4 model, Argon, landed at the end of September 2026 and opened up more widely in mid-October. I have been using it on the same work I run every week — agent workflows, test generation, long patches — and my honest reaction is that it is the first model where I stopped checking on a long task every few minutes.

But "it felt great" is not useful to anyone deciding what to pay for. So this post does two things: what Argon actually changed in my hands, and what the published benchmark tables say when you read them all the way across instead of just down the column Google highlighted.

What is actually new

Three things matter for the kind of work I do:

What changed in practice

The difference is not that Argon writes better sentences. It is that it keeps the thread.

On my agent work, the old pattern was: give a task, watch it lose the plot around the fifth step, restart with a tighter prompt. Argon holds a plan across many steps and keeps its own constraints straight — the schema it must satisfy, the endpoints it must not touch, the format the output has to be in. That is the difference between an agent I supervise and an agent I delegate to.

Two places it showed up immediately:

  1. Test generation. Asking for a module's tests used to produce a handful of happy-path cases and then stop. With the higher output ceiling I get the error branches and the edge cases in the same pass, which is exactly where the value is.
  2. Reading untrusted text. My automation pipelines ingest job listings and scraped pages. Argon is the most injection-resistant model Google has shipped, and that matters more for an agent than a couple of benchmark points. Google reports a 0.7% success rate for indirect prompt injection on Gray Swan's test, against 8.5% for GPT-6 Astra.

There is a cost to that willingness to work longer: it writes a lot more. Artificial Analysis measured roughly 62,000 output tokens for Argon against about 27,000 for Astra on the same evaluation set. If it picks the wrong direction, you pay for the whole detour. I now put a hard budget and an explicit "stop and report" instruction on long runs.

Published benchmarks, read properly

Google's comparison table covers 19 evaluations. Argon took first place outright on 13 and tied for first on one more. Here are the rows that matter for engineering work, compared with GPT-6 Astra and Claude Opus 5.5.

Coding

BenchmarkArgonGPT-6 AstraOpus 5.5Leader
DeepSWE v1.1 (long SWE tasks)77.9%74.1%74.2%Argon
FrontierSWE v255.0%65.5%62.3%Astra
Terminal-Bench 4.057.4%58.2%66.4%Opus 5.5
CWE-bench v1 (fixing security bugs)68%——Argon, tied for first

That first row is the one quoted everywhere: 77.9% on DeepSWE v1.1, a new high. The third and fourth rows are why I do not treat that as a general coding verdict. Argon is 10.5 points behind Astra on FrontierSWE v2 and about nine behind Opus on Terminal-Bench. Different tasks, different winners.

Long context, video and business work

BenchmarkArgonGPT-6 AstraOpus 5.5Leader
GraphWalks, 256k–1M BFS F184.2%71.8%66.8%Argon
LVBench (long video)91.7%87.5%83.7%Argon
AutomationBench (Zapier, end-to-end tasks)51.3%41.4%42.5%Argon
Vals Index (finance, legal, tax, coding)68.9%63.1%67.0%Argon

AutomationBench is the row I care about most, because it measures whether a model can complete a business task end to end rather than answer a question about it. 51.3% against 41.4% and 42.5% is roughly a nine-point lead — the largest gap anywhere in Google's table, and the closest thing to "does it finish the job".

Security

BenchmarkArgonGPT-6 AstraOpus 5.5Note
Gray Swan indirect prompt injection (lower is better)0.7%8.5%1.0%Argon best

Google also says Argon found a critical vulnerability in healthcare software used by hospitals worldwide that earlier frontier models missed, and that it is trained specifically for defensive cyber work. It shipped to trusted defenders without the usual cyber safety guardrails for that reason.

The independent numbers

Vendor tables are marketing until someone else runs the tests. Two independent sources are worth checking.

Artificial Analysis Intelligence Index. Argon at high reasoning scores 53, tying GPT-6 Astra at max (53) and one point above GPT-6.1 Sol (52). It sits about five points behind Claude Opus 5.5 and Sonnet 5.5. The more interesting number is the trend: that is a 23-point jump over Gemini 3.1 Pro Preview, Google's previous top model. On cost per index task, Argon came in at $1.99 during the launch discount — roughly 60% of Astra's $3.26 — rising to about $3.98 at list price, still under Opus 5.5 at $5.98.

BenchGecko's aggregate. An average of 89.2 across 24 public benchmarks, ranking 8th of 323 tracked models, with agentic work ranked #1 globally (82.4) and reasoning 5th (94.9). Its top individual scores are startling: 100% on the OTIS mock AIME set, 99.2% on GPQA Diamond, 99.0% on ProofBench, 98.5% on ARC-AGI and 91.3% on ARC-AGI-2. Epoch AI's index puts it at 166, 5th of 253 models.

The one number nobody quotes. On Artificial Analysis's factuality tests, Argon's reported hallucination rate was 15% against an accuracy of 50%, while Astra's accuracy was 63%. A lower hallucination rate is not the same as a higher accuracy rate — abstention, correct and incorrect answers have to be counted separately. For anything where a confident wrong answer is expensive, that is the number to design around, not the AIME score.

Where it loses, honestly

How I route work now

TaskModel I reach for
Long migrations, large patch sets, whole-suite test generationArgon
Agents that read untrusted content (listings, scraped pages, email)Argon
Terminal work, deployment scripts, failure recoveryOpus 5.5
The hardest held-out refactor where precise diffs matterAstra, with Argon as challenger
High-volume classification behind a deterministic regex gateCheapest flash tier that passes

Two practices make the cost work:

  1. Cache the stable part. Keep the system prompt, tool schemas and repo summary byte-identical across calls and the 95% cached-input discount applies. Put the changing instruction last.
  2. Budget the output, not the input. Argon earns its price by writing more. Give it a ceiling and an explicit instruction to stop and report if it is off-plan, or it will happily spend the whole budget exploring.

Bottom line

Argon is genuinely excellent at a specific thing: finishing long, messy, multi-step work without supervision. If your problem looks like an agent that has to hold a plan for twenty steps, or a task where the answer is forty thousand tokens long, it is the best thing I have used.

It is not the best model at every sub-skill inside that work. It trails on FrontierSWE, trails Opus in a terminal, and its factuality numbers need care. Treat the benchmark table as a map of where to start testing, not a ranking to buy.


Sources

All benchmark figures are as published by the sources above. Google's comparison table is vendor-reported; the competitor figures in it were not run by Google under identical harnesses.


Related

Author: Agu Chiedozie | Cloud & AI Systems Engineer