Skip to content

Name Auto as Copilot Fusion in Copilot agent host chat strings - #347198

Open
Bhavya U (bhavyaus) wants to merge 2 commits into
mainfrom
bhavyaus/copilot-fusion-naming
Open

Bhavya U (bhavyaus) wants to merge 2 commits into
mainfrom
bhavyaus/copilot-fusion-naming

Conversation

@bhavyaus

@bhavyaus Bhavya U (bhavyaus) commented Nov 9, 2026 •

Copy link
Copy Markdown
Collaborator

When the Copilot agent host presents its Auto model as Copilot Fusion, several user-visible strings in those chats still said "Auto". This names Copilot Fusion in them, and keeps the Auto wording when the host does not present Auto as Fusion.

What changes

  • Rate-limit errors: the suggestions to switch to Auto name Copilot Fusion.
  • Routing row: the fallback text shown when the router gives no reason reads "Copilot Fusion routed task to {0}", in the chat and in the accessible view.
  • On-device models: turn labels such as "Auto ({0})", the fallback and mixed-run reasons, the cloud fallback notice, the "Use Auto" actions, the model-ready offer, the picker's row notes and the "Use in Auto" switch.
  • Model picker label: the label shown while no model is selected uses the catalog's Fusion name instead of a hard-coded "Auto". The phone input label does the same.
  • Quota notification: "Switch to Auto to reduce credit usage" names Copilot Fusion.
  • Agent host process: the Fusion tier setting gets its own description, and the on-device server's crash, busy and load-timeout messages name Copilot Fusion.
  • Accessibility help: one sentence says the on-device strings name Copilot Fusion when Auto is presented that way.

How it is scoped

The wording switches on the autoModelFusion flag of the chat's own Auto model. That flag is only set from the model metadata that the Copilot agent attaches, so other agents and chats that are not agent host chats keep the Auto wording. Shared code such as the rate-limit messages takes the flag as an optional input that only the agent host session handler passes.

Model ids, setting keys, command ids and telemetry values are unchanged.

Not changed

The agent host setting titles "Use On-Device Model in Auto" and "Auto Optimize for Override" still say Auto. They are static setting text registered before the host knows whether Fusion is offered.

Bhavya U (bhavyaus) and others added 2 commits November 9, 2026 14:06
When the Copilot agent host presents its Auto model as Copilot Fusion, several user-visible strings still said Auto: rate-limit suggestions, the routing row fallback, on-device model labels and notices, the quota notification, and the model picker label shown while no model is selected.

These now name Copilot Fusion when the chat's Auto model carries the Fusion flag that the host advertises, and keep the Auto wording otherwise. Model ids, setting keys, command ids and telemetry values are unchanged.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
The On This Device rows looked for the Auto model's Fusion flag in a list already filtered to on-device models, so their notes kept saying Auto while the detail page said Copilot Fusion. The picker now passes the flag explicitly from its full model list.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copilot AI balanced review requested due to automatic review settings November 9, 2026 22:17

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot encountered an error and was unable to review this pull request. You can try again by re-requesting a review.

Note

This error may be related to your runner configuration. You can now configure runners for Copilot code review separately from Copilot cloud agent by creating a copilot-code-review.yml file with your setup steps. Read the docs for details.

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟡 Changes recommended

The existing Copilot Fusion routing test fails because its expected routing part omits the newly emitted fusion: true field.

1 open issue

Review effort: Balanced

const name = resolved && displayName(resolved);
return usageInfoToAutoModeResolution(usage, name);
const resolutionPart = usageInfoToAutoModeResolution(usage, name);
return resolutionPart && { ...resolutionPart, ...fusion };
@github-actions

github-actions Bot commented Nov 9, 2026

Copy link
Copy Markdown
Contributor

Screenshot Changes

Base: 7cadbfca Current: 74ac3f92

The screenshot report exceeds GitHub's comment size limit. View the full report in the workflow summary.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants