GitHub Copilot CLI Introduces Project HydraFusion Model Orchestration

GitHub CopilotView original changelog

GitHub Copilot CLI added Project HydraFusion, a research-preview feature that automatically routes each coding task across multiple AI models instead of relying on one model for the whole job, selecting from Single, Cascade, and Critique execution patterns based on task complexity. On GitHub's own benchmarks, HydraFusion matched or beat Claude Opus 5's task quality on TerminalBench 2.1 at 67% lower estimated cost, though it trailed slightly on two other benchmarks while still cutting cost substantially. It is available to every Copilot plan through /experimental in Copilot CLI.

Key Takeaways

  • HydraFusion automatically chooses between three workflows, Single, Cascade, and Critique, rather than requiring a developer to pick one model manually.
  • On TerminalBench 2.1, it beat Claude Opus 5's task quality by 4.9 points while cutting estimated cost by 67%.
  • On the other two benchmarks tested (DeepSWE, CheckpointBench), it came close to Opus 5's quality (within 1.5 and 0.1 points) at 36% and 65% lower cost, respectively.
  • The Critique workflow mirrors GitHub's earlier "Rubber Duck" second-opinion reviewer pattern, using a model from a different family to check another model's work.
  • It reached Hacker News's front page shortly after launch, with a mixed but engaged reception to the cost-versus-quality trade-off.
  • It's available to every Copilot plan, but only inside Copilot CLI via /experimental, not yet in VS Code, Visual Studio, or other surfaces.

Letting the Model Choice Choose Itself

Developers using Copilot CLI have long had to pick a single model for a task and hope it was the right trade-off between quality, speed, and cost. Project HydraFusion, now live as a research preview, removes that manual decision by treating workflow selection itself as something Copilot can optimize automatically. Instead of committing to one model up front, HydraFusion reads signals about a task's reasoning, code generation, debugging, and tool-use demands, then picks the least expensive workflow it expects will still clear the quality bar.

That workflow takes one of three shapes. In Single mode, one model handles the task directly, no orchestration needed. In Cascade mode, an efficient model drafts a solution first, and only escalates to a stronger, more expensive model if the draft doesn't meet quality standards. In Critique mode, one model drafts an answer, an independent reviewer drawn from a different model family critiques that draft, and the original model revises its work based on that feedback, a pattern similar to the "Rubber Duck" second-opinion reviewer GitHub introduced for code review agents earlier in 2026.

The Cost-Quality Trade-Off, By the Numbers

GitHub published benchmark comparisons against Claude Opus 5 and GPT-5.6 Sol run under matched task inputs, tools, and grading conditions. On TerminalBench 2.1, HydraFusion actually beat Opus 5's verified task quality by 4.9 percentage points while cutting estimated cost by 67%. On DeepSWE, a repository-level software engineering benchmark, it came within 1.5 points of Opus 5's quality at 36% lower cost, and on CheckpointBench, built from real Copilot session data, it landed within 0.1 points at 65% lower cost. In other words, HydraFusion undercut costs across every benchmark GitHub tested, but only outright matched or beat Opus 5's quality on one of the three, a trade-off that drew a mixed but engaged reception when the announcement reached Hacker News's front page.

Getting Started

HydraFusion is available to developers on every GitHub Copilot plan, but only inside Copilot CLI for now. To try it, a developer runs /update to get the latest CLI build, enables /experimental on, then selects HydraFusion (Research Preview) from /model like any other model option. Costs are calculated from the actual tokens consumed by whichever underlying models HydraFusion invokes for a given task, billed at each model's standard provider rate.