GitHub Copilot sets June 29 sunset for Opus 4.6 fast

Teams that pinned Opus 4.6 fast inside Copilot workflows have a short migration window. In a GitHub Changelog item published through RSS at 23:58:34 UTC on June 18, 2026, GitHub said it will deprecate Opus 4.6 fast across all GitHub Copilot experiences on June 29, 2026.

The scope is broad enough to matter operationally. GitHub lists Copilot Chat, inline edits, ask mode, agent mode, and code completions as affected surfaces. The deprecation table gives Opus 4.6 fast a 6-29-2026 removal date and points customers to Opus 4.8 fast as the suggested alternative.

For individual developers, this may look like a model-picker change. For enterprises, it is a configuration and governance event. Internal docs, model policies, IDE defaults, agent workflows, and any integration that assumes Opus 4.6 fast will continue to exist need to be checked before the deadline. The risk is not only that a preferred model disappears; it is that automated coding workflows behave differently when the model route changes.

GitHub’s guidance is aimed especially at Copilot Enterprise administrators. They may need to enable the alternative model through model policies in Copilot settings, then verify availability in individual Copilot settings and the model selector in VS Code or github.com. GitHub says no action is required to remove Opus 4.6 fast after deprecation, which means the migration work belongs before June 29.

The larger signal is that model lifecycle management is now part of developer-platform operations. Copilot is becoming a multi-model layer where availability, pricing, latency, and policy controls shift over time. Teams that use coding agents seriously will need routine checks for model sunsets, fallback behavior, and regression risk, not just benchmark comparisons. Opus 4.6 fast is the model leaving; the real lesson is that coding AI stacks now have dependency lifecycles of their own.