1d:I[70616,["/_next/static/chunks/0kcf5dt6yxdox.js","/_next/static/chunks/1su5n1uv1ti4s.js","/_next/static/chunks/0gvke1wv6udfg.js","/_next/static/chunks/1dfrle3jgmlzh.js","/_next/static/chunks/162lgvduyr-fa.js","/_next/static/chunks/2gcnnopam8e9w.js","/_next/static/chunks/2g60iab5a1pkg.js"],"Breadcrumb"] 1e:I[90762,["/_next/static/chunks/0kcf5dt6yxdox.js","/_next/static/chunks/1su5n1uv1ti4s.js","/_next/static/chunks/0gvke1wv6udfg.js","/_next/static/chunks/1dfrle3jgmlzh.js","/_next/static/chunks/162lgvduyr-fa.js","/_next/static/chunks/2gcnnopam8e9w.js","/_next/static/chunks/2g60iab5a1pkg.js"],"ArticleGrid"] 1f:T1c8f,

The most interesting number in GitHub's newest Copilot experiment is not a quality score but a bill: 67% less, on a hard terminal benchmark, while scoring 4.9 percentage points higher than Claude Opus 5. That is the headline result GitHub published for Project HydraFusion, a research preview that stopped asking which model should handle a coding task and started asking how many should, and in what order.

Key takeaways

HydraFusion beat a Claude Opus 5 baseline by 4.9 percentage points on TerminalBench 2.1 at 67% lower estimated cost, and roughly matched it on two other suites for 36% and 65% less.
Rather than routing to one model, it assembles a per-request plan that can draft, escalate, or bring in a read-only critic from a rival model family.
Every Copilot plan can switch it on inside the Copilot CLI, paying nothing extra beyond the standard token rate of whichever models the plan happens to invoke.

Why the cost line matters more than the quality line

Agentic coding has an economics problem that benchmark tables tend to hide. Teams that hand long, tool-heavy tasks to a frontier model pay frontier prices on every leg of the loop, including the legs that a cheaper model would have finished correctly. HydraFusion is GitHub's attempt to price each leg separately.

The evidence GitHub released comes from offline runs on three agentic suites, with Opus 5 and GPT-5.6 Sol as references and every model pinned to medium reasoning. Two of the three results are essentially parity buys: DeepSWE, which stresses cross-file repository work, finished within 1.5 points of Opus 5 for 36% less, and CheckpointBench came within 0.1 points for 65% less. Only TerminalBench 2.1 produced an outright quality gain, and GitHub notes that suite is comparatively saturated — which is part of why it ran the other two at all.

CheckpointBench is worth a second look because it is GitHub's own. The company assembled it from real Copilot session trajectories, anchoring each conversation to a public repository at an immutable commit so the run can be replayed, then balanced it across languages, task types and difficulty. It is closer to production traffic than a public leaderboard, and also impossible for anyone outside GitHub to audit.

The development record carries an unusually candid footnote: between 11 and 25 August, two operational failures inside the evaluation harness produced invalid runs that were thrown out before the trend line was drawn.

How a single prompt becomes a multi-model plan

HydraFusion reads capability signals — reasoning depth, code generation, debugging and tool use — and then picks the cheapest of three shapes it believes will clear the bar. One model may simply answer. Or a fast model drafts and a quality gate decides whether the draft ships or gets escalated to something stronger. Or, in the pattern GitHub likens to rubber-duck review, a drafter produces an artefact, a critic from a different model family reads it without any tools attached, and the drafter gets exactly one structured revision to respond.

Those thresholds were not set by hand. GitHub ran beam search over per-capability scores against a frozen baseline, tuning across all three suites at once instead of chasing any single one — the kind of choice that matters when the headline benchmark is the saturated one.

So far, the reasoning and task solving capability [of HydraFusion] is at or better than Opus.

That verdict came from a principal software engineer at Microsoft testing the system internally.

What GitHub had to lock down first

Pointing several models at one working tree introduces failure modes a single-model loop never has: a reviewer that edits the code it was asked to judge, a cancelled run that leaves a half-applied patch, a bill that nobody attributed because it was spread across six legs. GitHub's answer is a set of hard constraints — critics run tool-less and cannot write, patches are discarded entirely rather than partially applied when validation or cancellation intervenes, every leg carries a timeout and a cancellation handle, model bindings are verified before anything executes, and token spend is aggregated across drafting, critique, revision, escalation, retry and fallback so the whole workflow has one number attached to it.

Turning it on, and what it still cannot do

Access runs through the Copilot CLI: update the client, enable the experimental flag, and HydraFusion shows up in the model picker. The caveat is that a task which escalates twice or triggers a critique pass will cost more than the same task answered in one shot, because billing follows the models actually invoked.

GitHub is steering early users toward big, well-scoped, single-prompt work and says longer iterative sessions are the next engineering target. One rough edge it acknowledges up front: the preview withholds intermediate drafts until a single coherent answer is ready, on the reasoning that discarded work should not look finished — which in practice means staring at a progress indicator with little idea of what is happening. Feedback is being collected in the Copilot community thread.

Outlook

Treat the numbers as a hypothesis rather than a result. They are offline, tied to one model pool and one set of pricing assumptions, and the preview exists specifically to find out whether they hold when real developers throw messy work at it. If they do, the competitive question shifts away from whose model is strongest and toward who routes best — a shift that would suit a platform vendor with access to many providers rather better than it suits any single lab. It also arrives while GitHub is absorbing an agent-driven volume surge across its own infrastructure, which we covered in our report on the platform's commit growth.

FAQ

Is Project HydraFusion available outside the GitHub Copilot CLI?

Not yet. It ships only inside the Copilot CLI behind the experimental configuration. GitHub has given no timeline for bringing it to the IDE extensions or the Copilot app.

Does HydraFusion cost extra on top of a Copilot subscription?

No separate charge applies. You pay the normal token rate for each model the workflow calls, which means the price of a task varies with how many legs it takes to finish.

Which models does HydraFusion use?

GitHub has not disclosed the pool, describing it only as spanning multiple providers, and has said the critic is deliberately drawn from a different family than the drafter. Opus 5 and GPT-5.6 Sol served as evaluation baselines, not necessarily as pool members.

a:["$","div",null,{"className":"mx-auto max-w-7xl px-4 py-8 sm:px-6","children":[["$","script",null,{"type":"application/ld+json","dangerouslySetInnerHTML":{"__html":"{\"@context\":\"https://schema.org\",\"@type\":\"BreadcrumbList\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https://ainewsway.com\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"#github-copilot\",\"item\":\"https://ainewsway.com/tag/github-copilot\"}]}"}}],["$","script",null,{"type":"application/ld+json","dangerouslySetInnerHTML":{"__html":"{\"@context\":\"https://schema.org\",\"@type\":\"ItemList\",\"@id\":\"https://ainewsway.com/tag/github-copilot#itemlist\",\"name\":\"#github-copilot Articles\",\"numberOfItems\":1,\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"url\":\"https://ainewsway.com/articles/githubs-hydrafusion-stops-picking-a-model-it-builds-a-workflow-instead-mtzlbs36\",\"name\":\"GitHub's HydraFusion Stops Picking a Model. It Builds a Workflow Instead.\"}]}"}}],["$","$L1d",null,{"items":[{"label":"# github-copilot"}]}],["$","h1",null,{"className":"mb-8 text-3xl font-bold text-zinc-900 dark:text-zinc-100","children":["#","github-copilot"]}],[["$","$L1e",null,{"articles":[{"id":"a1eea49f-7efb-4f95-945f-15dfc4237829","slug":"githubs-hydrafusion-stops-picking-a-model-it-builds-a-workflow-instead-mtzlbs36","title":"GitHub's HydraFusion Stops Picking a Model. It Builds a Workflow Instead.","subtitle":"A Copilot research preview matched Claude Opus 5 on three agentic coding suites while cutting estimated cost by up to 67%","content":"$1f","excerpt":"GitHub's Project HydraFusion assembles a multi-model plan for every Copilot coding request, trading single-model simplicity for sharply lower cost.","coverImage":"https://cdn.ainewsway.com/uploads/2026/09/5614e906-0581-4945-8a40-4986c463e404.webp","coverImageCaption":"Source code on a developer screen: HydraFusion decides how many models should touch a task like this, and in what order.","authorId":"6773f67d-d7fa-4b19-8f38-384f10ac761b","status":"PUBLISHED","publishedAt":"2026-09-13T09:08:00.570Z","viewCount":0,"likeCount":0,"readingTime":6,"isFeatured":false,"isBreakingNews":false,"metaTitle":"GitHub HydraFusion: Multi-Model Routing Comes to Copilot","metaDescription":"GitHub's Project HydraFusion preview builds a multi-model plan per Copilot request, hitting +4.9pp task quality at 67% lower cost than Claude Opus 5.","metaKeywords":["GitHub HydraFusion","GitHub Copilot","multi-model orchestration","Copilot CLI","TerminalBench 2.1","AI coding agents","model routing","agentic coding"],"ogImage":null,"aiSummary":"GitHub has opened a research preview of Project HydraFusion, which builds a multi-model execution plan for each GitHub Copilot coding request instead of routing to one model. It chooses between direct answers, cascaded escalation and cross-family critique, and on TerminalBench 2.1 it improved verified task quality by 4.9 percentage points at 67% lower estimated cost than Claude Opus 5. It runs in the Copilot CLI on all plans at standard model token rates.","aiTags":[],"sentiment":null,"articleType":"ANALYSIS","videoEmbed":null,"videoType":null,"seoScore":85,"isAutoGenerated":true,"isBackfill":false,"pipelineStage":null,"copyrightScore":null,"similarityScore":null,"matchedSourceId":null,"createdAt":"2026-09-13T09:07:15.572Z","updatedAt":"2026-09-13T15:12:29.162Z","contentUpdatedAt":"2026-09-13T15:12:29.161Z","deletedAt":null,"author":{"id":"6773f67d-d7fa-4b19-8f38-384f10ac761b","name":"Seung Jung","username":"Seung Jung","avatar":null},"categories":[{"id":"32f2303b-b593-473f-bf9c-6a99acbe6ce1","name":"Developer Tools","slug":"developer-tools"}],"tags":[{"id":"10e9deed-b112-4a23-82c2-5e15f6fb109a","name":"GitHub Copilot","slug":"github-copilot"},{"id":"e33c0738-d08b-4b6d-81af-b4cac24c1a4b","name":"GitHub","slug":"github"},{"id":"18cdd61e-c75a-4aff-843e-db288dddc418","name":"Coding Agents","slug":"coding-agents"},{"id":"971d527f-0508-47c9-aac1-39914a5f883c","name":"AI Agents","slug":"ai-agents"},{"id":"ca8e24a6-cbd4-4bba-a596-bf5bbdafb5aa","name":"Microsoft","slug":"microsoft"}],"translations":[{"id":"6b5f4f35-9207-44dd-ad72-5dd21298d336","language":"ko","title":"GitHub 하이드라퓨전, 모델을 고르지 않는다. 워크플로를 짠다","subtitle":"Copilot 리서치 프리뷰가 에이전트 코딩 벤치마크 3종에서 Claude Opus 5와 대등한 성적을 내면서 추정 비용은 최대 67% 낮췄다","excerpt":"GitHub의 프로젝트 하이드라퓨전은 Copilot 코딩 요청마다 다중 모델 실행 계획을 짠다. 단일 모델의 단순함을 내주고 비용을 크게 낮췄다.","metaTitle":"GitHub 하이드라퓨전, Copilot에 다중 모델 배분 도입","metaDescription":"GitHub 프로젝트 하이드라퓨전 프리뷰가 Copilot 요청마다 다중 모델 계획을 짠다. Claude Opus 5 대비 품질 4.9%포인트 우위, 비용은 67% 절감."},{"id":"ff2275b4-ee83-4eb5-a39e-c95d516d9849","language":"ja","title":"GitHubのHydraFusionはモデルを選ばない。ワークフローを組み立てる","subtitle":"Copilotのリサーチプレビューが3つのエージェント系コーディングスイートでClaude Opus 5に並び、推定コストは最大67％削減","excerpt":"GitHubのProject HydraFusionは、Copilotのコーディング要求ごとに複数モデルの実行計画を組む。単一モデルの手軽さと引き換えに、コストを大幅に下げた。","metaTitle":"GitHub HydraFusion、Copilotに複数モデル振り分け","metaDescription":"GitHubのProject HydraFusionプレビューはCopilotの要求ごとに複数モデルの計画を組み、Claude Opus 5比で品質4.9ポイント上、コスト67％減を記録した。"},{"id":"b69d8cd3-cc58-45d7-8844-dcc84ce16368","language":"zh","title":"GitHub的HydraFusion不再挑模型，而是搭一条工作流","subtitle":"Copilot研究预览在三套智能体编程基准上追平Claude Opus 5，预估成本最多低67%","excerpt":"GitHub的Project HydraFusion为每个Copilot编程请求组装多模型执行计划，以单模型的简洁为代价，换来大幅更低的成本。","metaTitle":"GitHub HydraFusion：多模型调度进入Copilot","metaDescription":"GitHub的Project HydraFusion预览为每个Copilot请求组装多模型计划，任务质量较Claude Opus 5高4.9个百分点，成本低67%。"},{"id":"fe039b71-151e-493a-b0d2-60c1f3d881f1","language":"es","title":"HydraFusion de GitHub deja de elegir un modelo: monta un flujo de trabajo","subtitle":"Una vista previa de investigación de Copilot igualó a Claude Opus 5 en tres baterías de programación agéntica y recortó el coste estimado hasta un 67%","excerpt":"Project HydraFusion, de GitHub, arma un plan multimodelo para cada petición de Copilot y cambia la sencillez de un único modelo por un coste mucho más bajo.","metaTitle":"GitHub HydraFusion lleva el enrutado multimodelo a Copilot","metaDescription":"La vista previa Project HydraFusion de GitHub crea un plan multimodelo por petición de Copilot: 4,9 puntos más de calidad y un 67% menos de coste que Opus 5."}],"celebrities":[{"id":"4c975e87-2b02-46f5-a78d-1c8fc008bab7","nameKo":"깃허브","nameEn":"GitHub","slug":"github","profileImage":null}]}]}],"$L20"]]}]

#github-copilot

GitHubのHydraFusionはモデルを選ばない。ワークフローを組み立てる

ニュースレター購読

#github-copilot

GitHubのHydraFusionはモデルを選ばない。ワークフローを組み立てる