GitHub announced general availability of Copilot Fusion on October 28. Selecting it means choosing a model routing and orchestration system, rather than one specific model. Standard, High, and Max effort levels are available, and the announcement names VS Code, the Copilot app, CLI, and JetBrains. Charges follow the models used; involving additional models does not automatically lower the cost of every task.
Important context from the documentation
The current technical description says Fusion has no context window of its own: each step depends on the limits of its executing model. It also warns that discarding a draft does not automatically undo file changes already made. Fusion does not start subagents. Policies and subscription access constrain the model pool from which it can choose.
The administration guide separates Fusion configuration from general model availability. Permission in that list does not override the other policies applying to a user. Deployment therefore involves more than a new name appearing in the picker: an organization needs to understand which services can actually receive context.
What a useful pilot could establish
In our illustrative scenario, a team assigns a small fix, a change spanning several modules, and a task with insufficient information. We would assess final outcomes against criteria chosen beforehand, without changing task difficulty to suit a mode. The purpose would be to learn when additional review finds a real problem and when it merely extends the process. This is not a comparative experiment conducted by SIExpo.
For a failed draft, we would inspect the working directory too. An answer may have been revised while an intermediate file remains changed. Accepting the final explanation and accepting the actual set of changes are therefore separate decisions. Our pilot would use a recoverable copy, comparable starting states, and a review of the diff before merging.
The cost of the complete result
Our interpretation is that automatic selection moves part of the engineering decision into the system itself. That could simplify everyday work, but an organization still needs to explain its allowed models and final expenditure. We would record completed tasks, retries, and human review time, rather than comparing the length of one answer alone.
General availability is the substantive news. It does not establish identical results for every repository or make the highest effort level necessary for every change. The practical choice is to find a mode meeting specific requirements at an acceptable cost while preserving visibility into files. SIExpo has not changed Copilot settings or measured Fusion performance.
*AI illustration: a conceptual editorial image, not a documentary photograph or an actual product screen.*
*Editorial verification: 2026-10-29T07:14:17.195221+00:00.*
