GitHub Copilot Sets October 19 Model Retirement Deadline

The September 18, 2026 GitHub notice schedules six Copilot model retirements for October 19. Administrators should check replacement access now.

What GitHub announced on September 18, 2026

GitHub scheduled several Copilot model retirements for October 19, 2026. As of this article's October 16 check, that date is still upcoming. The notice covers Copilot experiences including chat, edits, agent mode, and completions. GitHub's official changelog provides the affected models and suggested alternatives.

Affected models and proposed replacements

GitHub says default model enablement can automatically enable alternatives for Business and Enterprise customers unless an administrator has disabled the relevant default or model. Administrators should inspect their own policies. A suggested replacement is a migration starting point, rather than a promise of identical behavior.

Editorial analysis: treat a retirement as a small migration

The first task is discovery. Ask teams which model they actually use and where that choice is recorded. Some people may select a model interactively while others rely on a saved preference or a documented workflow. An organization cannot evaluate the impact of retirement from its subscription list alone. A short inventory should connect the model choice to the task and the person responsible for it.

Then select representative work for a comparison. Include a routine code question, a bounded edit, and a task involving several files. Keep the repository state and instructions the same. Review whether the replacement understands the scope, uses the available context, and preserves important behavior. Record needed corrections rather than accepting the first plausible answer as evidence that the migration is complete.

For agent workflows, inspect the actions as well as the final patch. A replacement may choose a different sequence of searches, commands, or edits. That can affect the time required and the amount of review needed even when the final output looks similar. Use a reviewable branch or equivalent controlled workspace and compare the diff with the original request before applying the result elsewhere.

Communication should be specific enough to prevent confusion. Tell users which choices are changing, when the change occurs, where to select an alternative, and how to report a problem. Avoid describing the change as a general Copilot outage. A retired model is a particular service change, and clear language helps support teams distinguish an access-policy issue from a quality concern or an unrelated application failure.

Availability and limits

This report reflects the scheduled date in the September notice and the October 16 reporting check. It does not claim the retirement has already occurred. GitHub can update its supported-model information, and replacement visibility depends on the relevant experience and account policy. Readers should consult the current documentation and their administrator rather than relying only on a screenshot of a model picker.

What teams should verify before October 19

Confirm that the intended alternative is enabled for a small test group, then check the experience the team actually uses. A setting visible to an administrator is not the same evidence as a successful user session. Keep a record of who tested the replacement, what task was attempted, and whether any application or policy changes were needed to make it available.

Document a fallback for work that does not meet the acceptance threshold. That might be another supported model, a more tightly scoped task, or ordinary manual development. The important point is to preserve a way to complete the work while investigating a difference. A retirement deadline should not pressure reviewers into accepting code they do not understand.

Factual FAQ

Has the October 19 deadline passed in this report?

No. The reporting check is October 16, 2026.

Is manual removal of retired models required?

GitHub's notice says users do not need to remove the models after deprecation.

Additional primary-source context

GitHub’s supported-model reference provides the changing model catalog, while its access guide explains that availability depends on plan, client, and organization or enterprise restrictions. Together they explain why a suggested replacement may not appear in every user’s interface. Use the dated changelog for the retirement schedule and the current documentation for the access check; those sources answer different questions.

Supporting documentation: GitHub Docs: supported Copilot models; GitHub Docs: configuring model access.

Sources and reporting note

GitHub: official announcement (2026-09-18). Reporting checked on October 16, 2026. This article separates the announced facts from our editorial analysis; it is not a hands-on product test. Feature access and program terms can change after publication.