← Founder Notes
Archive

Github's new hydrafusion routes a single coding task across multiple models instead of betting on…

Yethikrishna ROriginal on Threads

github's new hydrafusion routes a single coding task across multiple models instead of betting on one, and github's own tests claim 36-67% lower cost than opus 5. the "which model do you use" question is about to sound quaint.

enterprises won't buy models anymore, they'll buy the router.

Context

GitHub's post of 4 September 2026 describes Project HydraFusion as a research preview in GitHub Copilot, on all plans through /experimental in Copilot CLI, billed at each underlying model's standard rate. It picks one of three patterns per request, Single, Cascade or Critique, across models from multiple providers. In GitHub's own offline evaluation with fixed policies, medium reasoning and Opus 5 as the baseline, it reports 67% lower estimated cost with 4.9 points higher on TerminalBench 2.1, 36% lower with 1.5 points lower on DeepSWE, and 65% lower with 0.1 points lower on CheckpointBench, GitHub's internal benchmark.

How it compares

These are vendor-run offline evaluations with estimated costs, specific to the benchmark revisions, configurations, model pool and pricing assumptions, and not independent. The routing policies were tuned across the same three benchmarks, and GitHub says TerminalBench 2.1 is relatively saturated. The 36 to 67% range leaves out that quality is lower on two of the three. Routing across models applies to Cascade and Critique, and Single uses one model. The post is dated 4 September, and the later availability status was not re-read here, so it is not presented as current. Enterprises buying the router is the author's forecast.

Related work

Watch next

  • Independent replication and later availability changes.

Sources

  1. Project HydraFusion (GitHub, 4 Sep 2026)github.blog

Provenance

The note above is reproduced unedited from the original post, first published on Threads on 19 September 2026 at 05:16 IST. Sources are the papers and datasets the note draws on.

View the original post
Embed this note
<iframe src="https://founder.myndlabs.tech/notes/embed/github-s-new-hydrafusion-routes-a-single-coding-DdcphC1igf4" width="480" height="420" style="border:0;max-width:100%" loading="lazy" title="Github's new hydrafusion routes a single coding task across multiple models instead of betting on…"></iframe>

More notes