Google Pairs Gemini 4 Hydrogen With Antigravity Coding Agents

ByMason Reed

November 14, 2026

Google’s new Gemini 4 Hydrogen model targets everyday coding and agent execution, while Antigravity’s Orchestrator hands implementation work between faster and more capable models.

Google is rolling out Gemini 4 Hydrogen, a model built for routine coding and other agent tasks, and pairing it with higher-end models in a new Antigravity workflow. The pitch for developers is practical: reserve deeper reasoning for planning and difficult decisions, then use Hydrogen to edit code, run tests and verify changes.

Hydrogen is available through the Gemini API and AI Studio, Android Studio, Google’s business products, the Gemini app and Search. In Antigravity, access to Orchestrator depends on subscription: Orchestrator (Carbon) is for Google AI Ultra users, while Orchestrator (Argon) is available to Pro and Ultra subscribers. Google says Hydrogen is also available directly to paid Pro and Ultra subscribers in Antigravity.

The model has four thinking settings — low, medium, high and xhigh — and a one-million-token context window. Google lists API pricing at $1.50 per million input tokens and $7.50 per million output tokens across that window. That gives small software teams a concrete starting point for comparing the cost of moving everyday work from a premium model to a faster execution model, though actual bills will depend on usage and task design.

Google reports a 57% score for Hydrogen on Terminal-Bench 4.1, compared with 18.2% for Gemini 3.8 Flash, and says Hydrogen completes tasks 2.5 times faster at its default high setting. In early partner tests, Google says it ran 2 to 2.8 times faster than Flash and used 12% to 23% fewer tokens. Those are company-reported results, not a guarantee that a given repository or agent setup will see the same gains.

The more notable product change may be how Antigravity divides work. Orchestrator starts with Carbon or Argon analyzing dependencies and making a plan in read-only mode. Hydrogen then carries out edits, package updates, tests and verification. If a run hits a failure or a decision that needs design judgment, control returns to the planner. Google also describes parallel workflows in which Carbon coordinates Hydrogen-powered worker and verifier agents in isolated workspaces.

That approach could help teams avoid paying for a frontier model to perform every mechanical step, while keeping a more capable model involved when judgment is needed. But it also adds an orchestration layer that developers will need to inspect: generated changes, test coverage, permissions and handoffs still require human oversight, especially in production systems.

There is a documentation wrinkle worth resolving before teams rely on the headline efficiency figures. Google’s Hydrogen announcement attributes Orchestrator’s near-Carbon success, 24% lower quota use and 19% faster completion to Terminal-Bench 4.0. Its Antigravity post cites the same figures against Terminal-Bench 4.1. The discrepancy does not erase the reported result, but it makes comparisons harder to evaluate until Google clarifies which benchmark version was used.

For builders, Hydrogen is worth testing on bounded tasks: repository questions, small bug fixes, package updates, test writing and web prototypes. Teams can compare it with their current model on the same work, tracking not just speed and token use but also failed edits and review time. Orchestrator is more relevant for users already inside Antigravity who want to experiment with model handoffs; it is not a universal tool for teams using other coding environments.

Google presents Hydrogen as an upgrade across consumer products as well as a developer model. For software businesses, however, the clearest case is the combination of published API prices, configurable reasoning depth and a workflow designed to separate planning from execution. The value will depend less on benchmark rankings than on whether those choices reduce the cost of shipping reliable code.

Leave a Reply

Your email address will not be published. Required fields are marked *