Plan with the big model, edit with the small one
Google's coding tool can now switch models in the middle of a task: an expensive model works out the plan, a cheaper one does the edits and runs the tests, and the expensive one steps back in only when the cheap one gets stuck.
ContextAntigravity is Google's agent-first coding environment; Gemini 4 Carbon and Argon are its top models, released earlier this week.
On November 12 Google released Gemini 4 Hydrogen, the cheapest model in the Gemini 4 family, and a new Orchestrator option in Antigravity's model menu. Orchestrator pairs Hydrogen with a stronger model in one task. Carbon starts read-only, explores the code and its dependencies, and writes a plan that includes when to re-plan. Hydrogen then makes the edits, updates packages and runs the tests.
If Hydrogen hits trouble, the task goes back to Carbon, which inspects the state, repairs the plan and lets Hydrogen resume. For parallel work, Carbon coordinates while Hydrogen runs worker and checker agents in separate workspaces.
Google reports that Orchestrator reached near-Carbon task success on Terminal-Bench while using about 24% less quota and finishing about 19% faster on average. These are the vendor's own numbers; no independent test of Orchestrator has been published yet.
Technical details
Hydrogen offers four thinking levels: low, medium, high (the default) and a new xhigh. Google cites 51 on the Artificial Analysis Intelligence Index at high (Argon scores 50) and 54 at xhigh, and 57% on Terminal-Bench 4.1 against 18.2% for Gemini 3.8 Flash. Google's two posts name different Terminal-Bench versions for the Orchestrator result (4.0 on blog.google, 4.1 on the Antigravity blog).
Availability: Hydrogen is in the Gemini API, AI Studio and Android Studio, and in Antigravity for paid AI Pro and Ultra plans. Orchestrator (Carbon) is for Ultra; Orchestrator (Argon) is for Pro and Ultra. The context window is 1 million tokens in and up to 1 million out, priced flat across it.
Antigravity's SDK lets you build the same split yourself, assigning models to roles. Google's example is an issue triage system where Hydrogen agents triage, code and ask clarifying questions, and a Carbon agent takes large refactors and security checks; no code for it is published yet.
Why it mattersPicking one model per session wastes money on easy steps or quality on hard ones. A planner and worker split is a pattern you can copy in any agent setup, and now there is a vendor measurement of what it saves.
For youThis is the same shape as a Claude Code main session delegating to cheaper subagents. Try a Fable planner with Haiku 5.5 subagents doing the edits and test runs on one plugin task, and compare cost and outcome against an all-Fable run.
- quota
- The amount of model usage a subscription allows in a period; cheaper models use less of it per task.
- Terminal-Bench
- A public benchmark that gives an agent real tasks to complete in a command-line environment and checks whether they work.
- read-only
- Allowed to look at files and run inspections, but not to change anything.
Sources Google Antigravity: Hydrogen and OrchestratorGoogle: Introducing Gemini 4 Hydrogen