The 30-Second Brief
- Source report GitHub retired six Copilot models across most experiences on October 19 and separately made model-policy REST controls generally available. [1] [2]
- Analysis Treat replacement selection, policy access and workflow testing as three separate migration checks. A model appearing in a selector does not establish that it is suitable for the same tasks.
Use the Effective-Date Replacement List
Source report The October 19 notice suggests these alternatives: [1]
- Gemini 3.7 Flash → Gemini 3.8 Flash
- GPT-5.5 and GPT-5.4 → GPT-6.1 Sol
- GPT-5.4 mini and GPT-5 mini → GPT-6 Luna
- Grok 4.5 → Grok 4.7
Source report GitHub asks users to update workflows and integrations. Enterprise administrators may need to enable replacement models in policy; no action is required to remove retired models. [1]
Policy Controls Are Now Programmable
Source report The new GET and PATCH endpoints cover enterprises, enterprise teams, enterprise apps and organizations. GitHub describes delegation to organizations in organization mode, or to teams and apps in enterprise teams mode. [2]
Analysis Begin with a read-only inventory. Identify who owns the policy at the relevant level, then compare intended availability with the developer’s actual experience. Avoid turning a missing-model complaint into a blanket enablement of every model. Programmable controls can make a small mistake repeatable across a large organization, so separate inventory from approved changes.
Test Behavior, Not Just Availability
Analysis Keep a compact regression pack: a familiar coding task, a repository-specific instruction, a tool-use boundary and a failure case the team already understands. Record the exact model and client used. Compare accepted results, review effort and task cost rather than relying on the replacement’s name. A staged rollout gives reviewers time to notice changed assumptions before those assumptions reach critical work.
Evidence & Uncertainty
Uncertainty These are GitHub’s supported-model and management announcements, not comparative performance tests. The suggested alternatives are not guarantees of equivalent outputs, costs or behavior. BriefSpire has not tested availability in a customer enterprise or benchmarked the replacements. The retirement notice says “most” experiences; do not silently expand that scope to every client configuration.
Story Timeline
September 18: advance retirement notice. October 19, 2026: effective retirement guidance and policy API announcement. October 20: BriefSpire source check. [1] [2]
Action Center
Selections remain in this browser.
Evidence Explorer
Does policy enablement prove the migration is complete?
Analysis No. It answers an access question. Workflow owners still need to validate behavior and document any changed assumptions.
Should the September notice be the final replacement checklist?
Use the effective-date notice linked here. Its replacement suggestions differ from the advance announcement. Preserve the date of the guidance used in your change record. [1]
Sources & Transparency
Last source check: . Both primary sources are from GitHub and are not independent confirmations. Migration sequencing and test design are BriefSpire’s analysis. No account policies or permissions were changed.