Google shipped Gemini 4 Hydrogen on November 12 and led with an uncomfortable benchmark: Hydrogen, the speed-tier model, outscores Argon on the Artificial Analysis Intelligence Index — the model it launched four weeks ago. That reorders some assumptions. Hydrogen is live now in the Gemini API under gemini-4-hydrogen, available on the free tier from day one.
Third Gemini 4 Model in Six Weeks
Gemini 4 Hydrogen is Google’s Flash successor — the workhorse tier designed for high-velocity everyday work: repository debugging, interactive web development, multimodal pipelines. It sits inside a 1,048,576-token context window shared by input, thinking, and output. Standard requests cap output at 65,536 tokens; background execution unlocks the full 1 million output side.
At the default “high” thinking level, Hydrogen scores 51 on the intelligence index versus Argon’s 50. Push it to xhigh and it reaches 54. On Terminal-Bench 4.1 — the agentic coding benchmark — Hydrogen hits 57% versus 18.2% for Gemini 3.8 Flash, its direct predecessor. It also cuts fabricated claims by more than 5x. The honest caveat: Argon still leads on HLE-Diamond (69.1% vs. Hydrogen’s 58.8%), so deep research tasks stay with Argon for now.
Four Thinking Levels — and a Cost Trap to Avoid
Hydrogen introduces xhigh thinking, a new tier above the existing low/medium/high options. Here is how to map them to actual work:
- low — fast chat, high-throughput classification, latency-sensitive pipelines
- medium — interactive coding, live UI prototyping
- high (default) — agentic coding, most debugging and refactor tasks
- xhigh — formal verification, hard math, long-horizon software engineering
The cost trap is xhigh on simple prompts. Google’s data shows average cost per task rises from .87 at high to .16 at xhigh, with nearly twice the output tokens consumed. If you are reaching for xhigh by default, you are paying Carbon prices for Hydrogen-tier work. Set high as the baseline and promote to xhigh only when the task demands it.
from google import genai
from google.genai.types import GenerateContentConfig, ThinkingConfig
client = genai.Client()
response = client.models.generate_content(
model="gemini-4-hydrogen",
contents="Refactor this function to handle null inputs and retry on timeout...",
config=GenerateContentConfig(
thinking_config=ThinkingConfig(
thinking_budget=8192 # "high" equivalent; set 0 to disable thinking
)
),
)
print(response.text)The Orchestrator Pattern: Dynamic Model Switching
The structurally interesting part of this launch is Orchestrator in Google Antigravity. Most agentic setups pick a model at session start and stay with it. Orchestrator abandons that. Carbon starts in a read-only phase: maps the codebase, identifies dependencies, writes a plan. Then Hydrogen takes over for execution: writes edits, updates packages, runs tests. If Hydrogen hits friction — an architectural decision, a subtle dependency conflict — Carbon re-engages, resolves it, then hands back to Hydrogen.
On Terminal-Bench 4.0, Orchestrator achieved near-Carbon task success rates while using 24% fewer quota units and completing tasks 19% faster than Carbon running solo. That is not a marginal improvement. That is the efficiency profile you want when you are running dozens of agent tasks in parallel.
The limitation worth noting: Orchestrator is currently available only inside Google Antigravity (Pro and Ultra tiers). API developers cannot yet replicate the automatic routing. You can build your own Carbon-to-Hydrogen handoff logic manually using the API, but the automatic session-level orchestration is Antigravity-exclusive for now.
Pricing
Standard rate: $1.50 per million input tokens, $7.50 per million output tokens — consistent pricing across the full 1 million-token context window. Batch and Flex API pricing cuts that in half: $0.75 input, $3.75 output. Free tier is available on Gemini API and AI Studio from day one. The official developer guide covers rate limits and quota allocation.
What to Make of This
The Orchestrator pattern is the real story here. A Flash-successor that outperforms the frontier model on the main intelligence index is a good headline. But the larger shift is in how Google is suggesting developers structure agentic workflows: not one model per task, but specialized models per task phase. Carbon thinks; Hydrogen acts. The handoff happens dynamically, not at session start.
That architecture will make its way to the API eventually. When it does, the question for developers building agent harnesses today is whether the abstractions they are using now will support dynamic model routing — or whether they will need to refactor. Worth thinking about before Orchestrator-style routing becomes the default expectation. Google’s full Gemini 4 Hydrogen announcement has the benchmark breakdowns and rollout timeline.
