GitHub Copilot Fusion Is GA: How to Choose Standard, High, or Max
The system routes and orchestrates models, while every model it uses is still billed at its standard rate
Key takeaways
GitHub made Copilot Fusion generally available on October 28, 2026. Instead of choosing a model for each step, users select Standard, High, or Max effort while Fusion routes and orchestrates models through single-model, cascade, or critique workflows. Administrators control which models Fusion may use and whether it is the default. The feature is available across all Copilot plans in VS Code, the Copilot app, Copilot CLI, and JetBrains IDEs. Each model used is billed at its standard rate; paid plans receive a temporary 30% discount on model costs. This guide shows how to compare the three effort levels with one task, fixed acceptance criteria, elapsed time, and complete usage evidence.
By ENHE AI · 2026-10-30 · AI-assisted drafting and editorial checks.
Direct answer: Effort levels are not fixed model names
Selecting Fusion means selecting a routing and orchestration system. Standard targets daily work, High addresses more complex problems, and Max spends more compute on the hardest tasks. The actual model combination can vary with the task and organization policy.
Three orchestration paths and administrator control
Fusion may use one model, a cascade that escalates from a faster model, or a critique flow where one model produces and another reviews. Administrators decide which enabled models Fusion may call, set the default effort, and may disable a model for Fusion independently.
Compare all three levels with one task
Choose a medium task with an existing test, such as fixing a reproduced edge case. Fix the starting commit, prompt, and acceptance criteria, then run Standard, High, and Max. Record test success, unrelated changes, human corrections, elapsed time, and AI usage.
Billing, discounts, and preview migration
Every model Fusion calls is billed at its standard rate. The 30% model-cost discount for paid plans is temporary and should not define a long-term budget. Users previously on auto, HydraFusion, or HydraFusion Max transition to corresponding effort levels and should recheck defaults.
Frequently asked questions
Is Max always better?
No. It spends more compute and is worthwhile only when it consistently reduces errors or human work against fixed acceptance criteria.
Can Fusion bypass a model disabled by an administrator?
No. GitHub says Fusion only uses models enabled by the enterprise and organization.
Why this matters
A multi-model system changes the question from which model to how much effort a task deserves. It reduces manual switching, but makes task-level records of quality, time, and cost more important.
Related tools and reading
These pages support the same task, workflow, or risk boundary.
- HydraFusion Max preview and task selection
- Copilot CLI discovers local Ollama models
- Hybrid AI agent local and cloud routing checklist
Conclusion
Use Standard as the baseline. Run all three levels on the same task, code state, and acceptance criteria, recording successful checks, human corrections, elapsed time, and actual usage. Reserve High or Max for tasks where the quality improvement consistently justifies additional cost.
What this means for everyday users
Every model Fusion calls is billed at its standard rate. The 30% model-cost discount for paid plans is temporary and should not define a long-term budget. Users previously on auto, HydraFusion, or HydraFusion Max transition to corresponding effort levels and should recheck defaults.
Related tutorials
[[zh]][[/zh]][[en]]Review a public website[[/en]]
SearchScope SEO/GEO
[[zh]][[/zh]][[en]]Access and usage guide[[/en]]
AI Prompt Management System | 418 Bilingual Prompts for Writing, SEO and AI Creation
High-Frequency AI Prompts for Work, Learning, and Teaching guide
High-Frequency AI Prompts for Work, Learning, and Teaching
Related reading
GitHub Copilot CLI Can Discover Local Ollama Models
GitHub updated Copilot CLI on October 7, 2026 so version 1.0.94-0 and later can discover supported models from a running local Ollama instance through the /model picker. Users can inspect the provider and endpoint, add a model, and use it in the current session without restarting the CLI. The workflow does not install Ollama or download model files, and compatible models must support tool calling and streaming. GitHub also highlights a privacy boundary that is easy to miss: selecting a local model does not automatically enable offline mode or disable GitHub telemetry. A remote provider may still receive prompts and code context even when offline mode is set. The practical task is therefore to verify the full route—runtime, endpoint, model capability, telemetry, tools, and outbound traffic—not merely the model label.
GitHub Introduces HydraFusion Max: When Multi-Model Review Is Worth Trying
GitHub has updated HydraFusion and introduced HydraFusion Max, an orchestration option for demanding coding work. It is not a new standalone model: the system chooses how to draft, review, or revise a response using models allowed for the account. Both options remain research previews, so access and suitability need checking before adoption. This article explains the distinction from automatic single-model selection and proposes a bounded bug-fix comparison that records tests, changes, and usage. It does not rank model quality or promise lower cost. The suggested exercise is designed for people already using an AI coding assistant who want to decide when additional review passes are worth the time and credits.
When Should an AI Agent Use a Local Small Model or the Cloud? A Hybrid Routing Checklist
AWS published an Adaptive Agentic Intelligence Framework guide using Strands Agents on October 21, 2026. The reference routes routine status checks and local vision work to small models through Ollama, while complex analysis goes to Amazon Bedrock. This durable guide helps teams decide when an AI agent should stay local and when it should use a cloud model. It classifies tasks, marks data that may leave the device, establishes local and cloud quality baselines, defines timeouts and fallbacks, applies one safety policy across both paths, and measures actual routing before estimating cost. The example can run on an 8 GB Raspberry Pi, but that hardware detail is not evidence that every workload belongs on a small local model.
GitHub Enterprise Starts Including Copilot Access: Fewer Seat Decisions, More Budget Control
GitHub announced on October 28, 2026 that enterprises working with a GitHub or Microsoft account team can include Copilot access for every licensed GitHub Enterprise Cloud user. The new access model does not include monthly AI credits per seat. AI usage is metered from the first request against the enterprise budget. Users without a GitHub Enterprise license can receive equivalent access through Copilot Standalone for $10 per user per month. Code completion and next edit suggestions continue without an available budget, while Chat, code review, and cloud features require budget. This article helps administrators verify eligibility, compare licensed and standalone populations, and prepare a controlled transition without disrupting current subscriptions.
How to Control Copilot Automations Cost: A Four-Layer Budget Checklist
GitHub expanded Copilot Automations on October 28, 2026 with external REST API triggers, 24 additional GitHub event triggers, 20 new tools, custom MCP tools, workflow chaining, and AI-credit limits for each run, day, week, or month. A per-run limit stops the current run when reached. Daily, weekly, and monthly limits prevent new runs until the relevant period resets. Automations without limits continue running under the existing behavior. This durable guide treats budgets as one control rather than a savings guarantee. It provides a sequence for bounding triggers and tools, setting four layers of limits, requiring approval for consequential actions, handling failure, and reviewing usage before expanding scope.
GitHub Copilot Can Generate and Edit Images: Check Cost, Watermarks, and File Output First
GitHub introduced a public preview for generating and editing images in Copilot on October 28, 2026. A user can describe an asset in VS Code, the GitHub Copilot app, or Copilot CLI. The selected reasoning model calls a dedicated tool powered by GPT Image 2.5 Flare, previews the result inline, and saves it into the project. The preview is available to Pro, Pro+, Business, and Enterprise plans. Image tokens are billed separately from the chat model against AI credits, and the visible “Made with AI” watermark is optional and off by default. This guide provides a bounded asset test covering input, output location, review, disclosure, and cost evidence.