Selected GitHub Copilot models deprecated
As of today, September 1, 2026, we have deprecated the following models across most GitHub Copilot experiences (including Copilot Chat, inline edits, ask.
By Dillip Chowdary • Sep 02, 2026 • Source: GitHub Changelog
What happened
words) Let's check length: "The update that takes effect on September 1, 2026, is not a traditional feature release but rather a structural deprecation of selected models within the GitHub Copilot ecosystem. This administrative cleanup removes older model options that previously powered a variety of user interfaces, forcing the system to route traffic to updated models instead. By executing this change, the platform ensures that the backend
Back to changelog As of today, September 1, 2026, we have deprecated the following models across most GitHub Copilot experiences (including Copilot Chat, inline edits, ask and agent modes, and code completions). Copilot Enterprise administrators may need to enable access to alternative models through their model policies in Copilot settings.
How it works
As an administrator, you can verify availability by checking your individual Copilot settings and confirming that the policy is enabled for the specific model. Once enabled, you’ll see the model in the Copilot Chat model selector in VS Code and on github.com.
Advertisement
Tech Pulse Daily
Get tomorrow's pulse first
Join engineers who read Tech Pulse before stand-up. Free, weekday mornings.
Why it matters
GitHub Enterprise customers with questions or concerns are encouraged to reach out to their account manager for further assistance. See the full write-up from GitHub Changelog via the source link for quotes and complete context.
Who is affected
Read the original coverage at GitHub Changelog via the source link above for the complete details and primary quotes.
What to watch next
Cross-check release notes and official docs before changing production systems based on early reporting.
Developer Action Items
- ☐ Diff the official changelog for GitHub / Copilot before you bump — APIs, defaults, and removed flags only.
- ☐ Install through the vendor's documented channel in staging; keep a one-command rollback and time-box the canary.
- ☐ Grep your repo for old flag names, lockfile pins, and plugin versions that the notes mark as breaking.
- ☐ Prefer the first patch cut over the day-zero tag unless you have a reason to be on the leading edge.
- ☐ If GitHub Changelog did not name a region, plan, or SKU, screenshot the official availability line before you promise it to users.
Author
Dillip Chowdary
Writes Tech Bytes coverage of AI, engineering, and the tools that actually ship. Editor of Tech Pulse Daily.
Related on Tech Bytes
Advertisement