GitHub announced Project HydraFusion on September 4, 2026, a project available as a research preview within GitHub Copilot for orchestrating AI models from multiple providers while performing programming tasks. Rather than selecting a single model in advance, HydraFusion creates an execution plan and determines whether the task requires a direct solution, independent review, or escalation to a more capable model.
The move follows the Auto model selection feature that GitHub launched earlier in the year to choose the most suitable model for each task. However, HydraFusion expands the idea from model selection to building a complete workflow that balances result quality, cost, and response time, while the operational complexity remains hidden from the developer, who selects HydraFusion just as they would any other model in Copilot.
Three paths for executing a task
The system evaluates signals related to reasoning, code generation, debugging, and tool use, then selects one of three execution modes:
- Single: A single model handles the task directly when its capability is sufficient.
- Cascade: A more efficient model begins by formulating the solution, after which a quality gate decides whether to accept it or refer the task to a more capable model.
- Critique: A model formulates an initial solution, then an independent model from a different family reviews it in a read-only context, before the first model performs one revision of the solution.
GitHub says the purpose of selectivity is to use additional calls only when they are expected to improve the result. Thus, the direct path preserves speed and efficiency, while the other two paths add review or escalation for tasks that benefit from them.
What the tests showed
GitHub evaluated fixed HydraFusion policies on three coding-agent benchmarks: TerminalBench 2.1, DeepSWE, and the internal CheckpointBench built from real sessions in GitHub Copilot. The results were compared with two baselines, Claude Opus 5 and GPT-5.6 Sol, using identical inputs, tools, execution limits, pricing assumptions, and evaluation conditions.
On TerminalBench 2.1, HydraFusion achieved a 4.9-percentage-point improvement in the quality of verified tasks, while reducing the estimated workflow cost by 67% compared with Claude Opus 5. On DeepSWE, which focuses on repository-level software-engineering tasks and understanding dependencies between files, the system came within 1.5 percentage points of Opus 5, at 36% lower cost. On CheckpointBench, the quality difference was only 0.1 percentage points, with a 65% cost reduction.
The cost accounting includes all execution stages, including formulation, review, revision, escalation, retries, and fallback plans. However, GitHub describes these results as offline tests limited by the benchmark versions, workflow settings, model set, and pricing assumptions used.
Operational controls and preview limitations
GitHub designed HydraFusion around controls that include recording cost and usage for each stage, setting cancellation and execution timeouts, and isolating review steps in contexts with no tools and no ability to modify the repository. The system also prevalidates workflow definitions, model mappings, fallback behavior, and model availability, and applies no correction if the process is canceled or validation fails.
GitHub currently recommends beginning the trial with large, well-defined programming tasks submitted in a single prompt to Copilot in automatic mode. The company will later focus on improving the performance of longer, multi-turn sessions. It also cautions that models, workflows, names, availability, and product behavior may change during the preview period.
Editorial reading: from model selection to workflow design
The most important change here is not the addition of a new model, but the transfer of the execution decision from the developer to an orchestration layer that decides when one attempt is sufficient and when a task justifies the cost of review or escalation. If the test results carry over to actual usage, this could give developers quality close to that of more capable models for some tasks without paying their cost for every request.
However, the figures do not yet establish a general advantage across all programming patterns; they are tied to specific benchmarks, controlled policies, and offline results. Questions about response time, reliability, system behavior in long sessions, cache efficiency, and safety remain open, and GitHub has said it will measure these aspects during the preview.