Agent Upstart

Cool things people are building with agents — and practical help getting the most out of them.

Playbooks · Coding tasks

Copilot Fusion is generally available: what it does to your AI-credit bill

Written October 31, 2026

For a Copilot user turning on Fusion: you stop picking a model and pick an effort level instead, and Copilot routes each task to one or more models. That routing can save credits on everyday work and spend more of them on hard work — the bill follows how many models answer, not the effort level you picked.

What changed

GitHub made Copilot Fusion generally available on 28 October 2026. Instead of selecting a model in the model picker, you select Copilot Fusion and choose an effort level: Fusion Standard, Fusion High, or Fusion Max. Fusion then chooses the execution pattern and the models for each prompt. It is available in Visual Studio Code, the GitHub Copilot app, GitHub Copilot CLI, and JetBrains IDEs, on all Copilot plans, according to GitHub's changelog. Fusion brings together Project HydraFusion's multi-model orchestration and Copilot auto model selection's model selection, per the same changelog.

Fusion chooses one of three execution patterns per prompt, as GitHub's Fusion documentation describes them: Single, where one model completes the task; Cascade, where an efficient model drafts a solution and a judge decides whether to accept it or escalate to a stronger model; and Critique, where one model drafts a response while multiple models critique it in parallel, and the original model revises from the combined feedback. Different prompts in one session can use different patterns. Fusion only uses models enabled in your plan and your organization's policies, and administrators can set Fusion as the default for users under Enterprise managed settings.

How the billing works

There is no separate charge for Fusion itself. GitHub's documentation states the rule plainly: when you use Copilot Fusion, you are billed for each model it uses, at that model's standard rate. Because Fusion High and Fusion Max can use more than one model for a task, a task may consume more AI credits than it would with Fusion Standard. Fusion Standard selects one model for each task, so a straightforward task under Standard behaves like a request to one model. The documentation also states that Fusion only adds model calls when a task warrants them, so a straightforward task does not wait or use credits for a review it does not need, and that routing happens along natural cache boundaries to avoid additional cache-related costs.

AI credits are the billing unit: 1 AI credit equals $0.01 USD, and each interaction is priced by the tokens it consumes at the rate of the model used. Monthly allowances on individual plans, from GitHub's plans page, are 1,500 credits for Copilot Pro ($10 a month: 1,000 base credits plus a 500-credit flex allotment), 7,000 for Copilot Pro+ ($39), and 20,000 for Copilot Max ($100). Unused included credits do not carry over between months. There is no published fixed credit charge for a Fusion task, because the charge depends on which models Fusion calls and how many tokens each one uses.

Through 30 November 2026, users on paid Copilot plans receive a 30% discount on model costs when using Copilot Fusion, according to the Fusion documentation. The changelog calls the discount limited-time without naming an end date; the documentation names 30 November 2026. Treat the discount as a window that ends on that date, not as a standing price: after it ends, the same Fusion task costs its full per-model rates.

Strengths

Weaknesses and limits

What to do about it

  1. Start on Fusion Standard. It selects one model per task, so its cost behaves like picking one model yourself, and it is the level where the routing saves credits by moving you off a powerful model after a hard task.
  2. Check your usage dashboard after your first High or Max tasks. GitHub's billing documentation states that the usage dashboard shows your available allowance and what you have used. Compare the credits a task consumed against the same kind of task under Standard before making High or Max your default.
  3. Do not budget on the 30% discount past 30 November 2026. Price any ongoing Fusion use at full per-model rates, and recheck the documentation after that date rather than carrying the discount forward.
  4. Review every Fusion session's changes before committing. A discarded draft's edits stay in your workspace. Read the diff before the commit, whatever effort level ran.
  5. Keep the effort level per task, not per week. Use Standard for everyday work, and reserve High or Max for a substantial, well-scoped task where extra model calls may be worth the extra time and credits, as the documentation frames those levels.

Limits of this evaluation

Related playbooks

Sources

Back to: Coding playbooks hub · Also: Review a pull request with a coding agent · Onboard onto an unfamiliar codebase with an agent · Agent cost estimator