Google's new Orchestrator system can complete coding tasks 19% faster while consuming 24% less quota than using a frontier model alone. By dynamically switching between the high-efficiency Gemini 4 Hydrogen and the high-reasoning Gemini 4 Carbon, the system maintains near-frontier success rates while significantly reducing latency and resource consumption.

This image serves as the primary visual for the announcement of the Gemini 4 Hydrogen model and the Orchestrator system.
Gemini 4 Hydrogen and the Limits of Static Routing
Gemini 4 Hydrogen is a standalone model optimized for routine coding tasks, debugging, and agentic workflows. It offers four thinking levels—low, medium, high, and a new 'xhigh' tier—to balance reasoning depth with speed.
While many industry solutions use a static 'model router' to guess task difficulty from an initial prompt, these often fail as tasks evolve. Long-running agent tasks frequently require different levels of complexity at different stages, which a single initial routing decision cannot account for.
“Orchestrator takes a dynamic, bidirectional approach between Carbon and Gemini 4 Hydrogen within the evolution of a single trajectory.”
— Gemini 4 Hydrogen and Orchestrator | Google Antigravity Blog
Dynamic Orchestration Between Carbon and Hydrogen
The Orchestrator feature addresses the limitations of static routing by using a dynamic, bidirectional approach between Gemini 4 Carbon and Gemini 4 Hydrogen. Instead of a one-time decision, the system adjusts the model based on the current state of the task trajectory.
For example, Carbon can initiate a read-only phase to explore dependencies and build a concrete plan with re-planning triggers. Hydrogen then takes over to perform execution tasks like writing edits, updating packages, and running tests. If Hydrogen encounters friction, the Orchestrator hands the state back to Carbon to repair the plan and resume execution.
This image illustrates the Carbon model, which handles high-reasoning tasks and plan repairs within the Orchestrator workflow.
Performance Gains and Developer Control
Testing on Terminal-Bench 4.1 demonstrated that Orchestrator reached success rates near those of the Carbon model while being significantly more efficient. This balance allows users to maintain high-quality output without burning through frontier-level quotas on every routine step.
For users requiring precise control, the Antigravity SDK allows for programmatic model pairing. This enables developers to build custom pipelines, such as an issue triage system where Hydrogen agents handle high-volume coding and UI iterations while a Carbon agent is reserved for security checks and large-scale refactors.
Availability and Limitations
Gemini 4 Hydrogen is currently rolling out to paid Google AI Pro and Ultra subscribers, while the Orchestrator feature is initially available for Google AI Ultra subscribers. Enterprise access is provided through Gemini for business.
While the Orchestrator automates the handoff between models, the specific internal logic and technical triggers for these bidirectional transitions remain internal details. The system's effectiveness relies on the models' ability to accurately signal when a task has hit 'friction' requiring a higher reasoning tier.
What Hacker News readers are saying
- Alternative: One commenter noted that similar multi-model pipelines already exist in products from Anthropic and GitHub, questioning how these systems manage efficient caching across different models. comment ↗
- Skeptical: A user expressed concern about delegating model selection to an automated orchestrator, noting that models can be overconfident about their own capabilities compared to manual subagent configuration. comment ↗
- Skeptical: Another commenter argued that the cost-saving benefits of the new system might not outweigh the perceived lower value of the platform compared to competitors like Claude or GPT. comment ↗
Summarized opinions from the Hacker News thread, not verified facts. Read the full discussion ↗