GitHub brings HydraFusion model orchestration to more coding apps
GitHub expands HydraFusion to VS Code and the Copilot app with model orchestration, preview limits and usage costs
GitHub expanded HydraFusion to Visual Studio Code and the Copilot app on September 30. The research preview coordinates models within a coding task and now reaches developers beyond its original command line interface.
The preview reaches more editors
The release lists Copilot Pro, Pro+, Business and Enterprise users. VS Code requires version 1.140 or later, or Insiders. The Copilot app needs its latest version and the HydraFusion setting enabled. Business and Enterprise administrators must allow preview features.
GitHub introduced HydraFusion on September 4 through Copilot CLI. The later release broadens access to that existing system. Its central idea is to choose both the models and the sequence of work for each request.
A workflow chosen for the task
The system can use one model directly, ask a cheaper model to try first and escalate if a quality check requires it, or have a second model review a draft. In the review pattern, the critic comes from a different model family and the original drafter revises once.
Those choices have different tradeoffs. Additional review can help with demanding work, while a simple task may need only one pass. GitHub’s early performance results come from controlled offline evaluations. They do not establish the cost or quality a particular team will see.
Extra model passes affect the bill
The current usage guide says every model used is billed at its standard rate. HydraFusion has no separate fee, but the Auto selection discount does not apply. Multiple passes can take longer and consume more AI credits. Model choices must fit the user’s plan and organization policies, and users cannot select the underlying mix.
Discarded drafts can leave file changes
The guide warns that rejecting a draft does not automatically reverse edits it already made in the workspace. The preview has no service level agreement and is not intended for production workloads. Its available models and execution patterns can change.
A useful trial should track the final patch, test results and total usage together. Inspect the working tree before committing, including edits that a discarded draft may have left behind. ByteForward reviewed the release and documentation but has not independently run HydraFusion.
Illustrative archival photograph by Christina Morillo under CC0. Resized and converted to WebP. It shows people working at laptops, without a HydraFusion session.
