GitHub has introduced Project HydraFusion, a research preview that dynamically orchestrates multiple AI models to handle coding tasks. Instead of picking one model upfront, HydraFusion selects a workflow—single, cascade, or critique—and routes each task to the models that best balance quality, cost, and latency. It's available now via /experimental in GitHub Copilot CLI.

How HydraFusion Works

For each request, HydraFusion evaluates signals for reasoning, code generation, debugging, and tool use, then picks one of three execution patterns:

• Single: one model solves the task directly – fastest and cheapest when it suffices.
• Cascade: an efficient model drafts a solution, and a quality gate decides whether to accept it or escalate to a stronger model (e.g., Claude Opus 5).
• Critique: one model drafts, an independent read-only critic from a different model family reviews the output (without tool access, so it can't modify the repo), and the drafting model revises once.

This mirrors how developers already work manually—choosing a model, asking for a review, or escalating a hard problem—but automates it inside the runtime.

Benchmarks: Quality Up, Cost Down

In offline evaluations on TerminalBench 2.1, HydraFusion improved verified task quality by 4.9 percentage points while cutting estimated cost by 67% compared to running Claude Opus 5 solo. The efficiency comes from using small models for easy tasks and reserving frontier models for the steps that need them.

Operating Principles

HydraFusion is built on five guardrails to keep execution predictable:

• Complete accounting: aggregates cost/usage across every leg—drafting, critique, revision, escalation, retry, fallback.
• Bounded execution: explicit timeouts and cancellation for each leg to cap cost and runtime.
• Isolated review: reviewers run in tool-less contexts so they can't modify the repo; solvers get the shared workspace.
• Fail-safe application: no patch is applied if a workflow is cancelled or fails validation.
• Validated routing: workflow definitions, model bindings, and fallbacks are verified before execution.

How to Try It

HydraFusion is in research preview for all GitHub Copilot plans. To use it:

# Update Copilot CLI to latest
/update

Enable experimental mode
/experimental on
Select HydraFusion from the model picker
/model → select HydraFusion (Research Preview)

Usage is billed at the standard token rate for whichever models HydraFusion invokes. Feedback can be posted in the GitHub Community.

HydraFusion is part of GitHub's broader push toward automated semantic routing between local, cloud, and compound models. As new models ship in Copilot, they can be folded into the routing pool without changing the user experience.