# GitHub Copilot HydraFusion: Multi-Model Orchestration, 67% Lower Cost > Source: > Published: 2026-09-12 01:07:12+00:00 GitHub shipped Project HydraFusion into Copilot CLI on September 4. Instead of routing your request to a single AI model, it builds a fresh execution plan for every task — orchestrating models from multiple providers to draft, critique, and revise your code. In offline benchmarks on [TerminalBench 2.1](https://www.vals.ai/benchmarks/terminal-bench-2-1), it improved verified task quality by 4.9 percentage points over Claude Opus 5 while cutting estimated cost by 67%. That combination is hard to ignore. ## Three Workflows, One Runtime Decision The core idea is simple to state and genuinely hard to execute: stop asking the user to pick a model and let the system pick the right *workflow* for each specific task. HydraFusion ships with three patterns today. **Single.** One model handles the task start to finish. Fast, cheap, appropriate for boilerplate and simple completions. **Cascade.** An efficient model drafts first. A quality gate evaluates the result. If the draft passes, you pay cheap-model prices. If it fails, the system escalates to a frontier model and tries again. Most tasks never reach the escalation step. **Critique.** A drafting model produces a solution. A second, cross-family model then independently reviews it in isolation — no repo access, no ability to change anything — before a single revision. The reviewer is structurally prevented from making changes; it can only evaluate. HydraFusion selects among these at runtime based on the task. You do not configure which pattern to use. The system does. ## The Engineering Is the Feature Research previews are easy to ship. Production-grade multi-model orchestration is not. GitHub published five operating principles that govern how HydraFusion runs, and they reveal what makes this harder than it looks. - **Complete accounting.** Every workflow leg — drafting, critique, revision, escalation, retry, fallback — rolls up into a single cost total. No hidden per-model charges buried in usage logs. - **Bounded execution.** Each leg has explicit timeout and cancellation behavior. The system cannot silently run over budget. - **Isolated review.** Review steps run in stripped-down, tool-less contexts. The reviewer model reads but cannot modify the repository or call external tools. - **Fail-safe application.** If the workflow is cancelled or fails validation, no partial patch is applied. The repo stays clean. - **Validated routing.** Before execution begins, HydraFusion verifies model bindings, fallback behavior, and whether selected models are actually available. These are not marketing bullets. They are the constraints that turn a demo into something you can depend on in production. ## Model Selection Is Now a Commodity Satya Nadella framed HydraFusion as “the shift from model selection to model orchestration.” That is worth sitting with. Cursor and Windsurf let you pick a model. That is a user-experience feature dressed as a technical differentiator. HydraFusion argues that individual model selection is the wrong abstraction entirely. The question is not which model is best — it is which combination of models and workflow patterns produces the best result for *this specific task* at a cost the team can sustain. HydraFusion also routes across multiple providers by design — Anthropic, OpenAI, and others. No vendor lock-in baked into the architecture. GitHub is positioning Copilot as the orchestration layer, with model providers as fungible inputs. ## How to Enable It Now HydraFusion is live in [GitHub Copilot CLI](https://github.com/orgs/community/discussions/206492) on all plans — Individual, Business, and Enterprise. VS Code support is targeting September. To try it today: 1. Open GitHub Copilot CLI and run `/update` to ensure you are on the latest version. 2. Run `/experimental on` to enable experimental features. 3. Run `/model` and select**HydraFusion (Research Preview)** . ## The Honest Caveats HydraFusion is a research preview. The benchmark numbers come from [offline evaluations](https://github.blog/ai-and-ml/github-copilot/project-hydrafusion-frontier-quality-via-multi-model-orchestration/) on TerminalBench 2.1. GitHub also tested on DeepSWE and an internal CheckpointBench; those results were “matched or nearly matched” — not the headline improvement. Real-world results on your codebase will vary. CLI only for now. The VS Code and Copilot app integrations are targeting September, alongside the [unified Copilot experience](https://www.developersdigest.tech/blog/github-copilot-september-policy-billing-reset-2026) rolling out September 28. If multi-model orchestration delivers even half the efficiency gain in production that it shows in benchmarks, it changes the cost calculus for teams running Copilot at scale.