GitHub Copilot models deprecated on November 16, 2026
GitHub deprecated Claude Opus 4.8, Claude Opus 5, and GPT-5.6 Terra on November 16, 2026, transitioning developer accounts to Claude Opus 5.5 and GPT-6 models.
By Dillip Chowdary • Nov 16, 2026 • Source: GitHub Changelog

At a glance
- Product
- GitHub Copilot
- Deprecation date
- November 16, 2026
- Announcement date
- October 15, 2026
- Retired models
- Claude Opus 4.8, Claude Opus 5, GPT-5.6 Terra
- Replacement models
- Claude Opus 5.5, GPT-6.1 Sol, GPT-6 Luna
- Annual plan exception
- Claude Opus 4.8 kept for individual annual subscribers
In this post
GitHub officially deprecated multiple legacy artificial intelligence models across its core programming surfaces on November 16, 2026, putting an end to standard production availability for three prominent systems. According to GitHub Changelog's report, the retirement impacts Copilot Chat, inline code edits, ask and agent modes, and automated code completions. The platform previously signaled this architectural change on October 15, 2026, giving engineering teams a month of advance notice to prepare integrations.
This report breaks down the specific model removals, replacement options, administrative policy controls, and workflow migration pathways for software organizations. Engineering leaders, enterprise administrators, and individual developers using GitHub Copilot must review how these transitions affect automated agents, code suggestions, and IDE settings. Understanding the updated model roster ensures developer environments remain uninterrupted during routine coding and enterprise automated code generation tasks.
01Deprecated models across GitHub Copilot environments
GitHub structured this deprecation wave to phase out older foundation models that previously powered core editor tools. The scheduled retirement specifically removes Claude Opus 4.8, Claude Opus 5, and GPT-5.6 Terra from standard developer workflows. Each of these model tiers has now reached its formal retirement milestone across the broader ecosystem of supported GitHub developer tools.
The operational scope covers nearly every standard user interaction point across the software lifecycle. Developers will observe changes within Copilot Chat conversational panels, inline editor code modifications, agent execution modes, contextual question prompts, and standard code completions. These interfaces now redirect interaction requests toward modern generation engines to maintain consistent performance and up-to-date coding capabilities.
02Model retirements and suggested migration targets
To maintain service continuity, GitHub identified direct migration targets for each retired generation model. Developers shifting away from Claude Opus 4.8 and Claude Opus 5 are directed to adopt Claude Opus 5.5 across all active editor surfaces. Meanwhile, workflows previously configured around GPT-5.6 Terra must move to either GPT-6.1 Sol or GPT-6 Luna depending on specialized project requirements.
| Model | Deprecation date | Suggested alternative |
|---|---|---|
| Claude Opus 4.8 | 2026-11-16 | Claude Opus 5.5 |
| Claude Opus 5 | 2026-11-16 | Claude Opus 5.5 |
| GPT-5.6 Terra | 2026-11-16 | GPT-6.1 Sol or GPT-6 Luna |
The model transition provides organizations with clear upgrade paths that align with current generation architecture. Claude Opus 5.5 serves as the single unified consolidation target for the retiring Claude line, eliminating parallel maintenance across separate intermediate versions. Teams relying on GPT architecture receive two distinct migration choices with Sol and Luna, enabling developers to choose the model configuration best suited to their engineering workloads.
03Runtime refusal fallbacks and subscription exceptions
Advertisement
Tech Pulse Daily
Get tomorrow's pulse first
Join engineers who read Tech Pulse before stand-up. Free, weekday mornings.
While general availability has ended, GitHub maintained specialized operational pathways for select developer scenarios. Claude Opus 5 has been officially removed from the visual model selector menu across all user-facing tools, preventing developers from manually choosing it for new tasks. However, the model remains active behind the scenes for automated runtime refusal fallback processes when requests possess existing authorized access.
Note: Claude Opus 4.8 is still available to individual GitHub Copilot subscribers on annual plans. This provision ensures annual account holders maintain access to the legacy system, whereas standard accounts and organization seats transition directly to the designated replacement models.
Organizations operating under enterprise agreements retain their current governance baselines throughout this transition. Existing enterprise model policies continue to apply without retroactive invalidation, ensuring that centralized corporate compliance controls remain enforceable across technical teams. This distinction enables organizations to transition internal tooling smoothly without unintended disruptions to underlying authorization frameworks or security parameters.
04Enterprise policy controls and model selector visibility
Account management configurations dictate how replacement models appear inside developer tools for commercial teams. Under default model enablement settings, the suggested alternative systems are automatically activated for Copilot Enterprise and Copilot Business customers. This automatic provisioning ensures that developers gain immediate access to upgraded model engines without requiring manual configuration from organization managers.
Manual administration is required only when corporate security teams have customized their defaults. If an administrator previously deactivated the global default setting or explicitly blocked a specific model, replacement systems remain dormant until updated. In those circumstances, administrators must navigate to Copilot settings and adjust their organizational model policies to grant explicit access to Claude Opus 5.5, GPT-6.1 Sol, or GPT-6 Luna.
Once an administrator verifies enablement within the centralized dashboard, developers immediately see the active replacement models inside their Copilot Chat model selector. Furthermore, administrative teams do not need to perform manual cleanup operations to purge retired models from interface dropdowns. The system automatically prunes deprecated endpoints from the client selector across all supported GitHub Copilot applications.
05Workflow updates and enterprise account assistance
Development teams are advised to review automated pipelines, scripts, and custom integrations to ensure external systems reference supported endpoints. While editor interfaces refresh automatically, custom API calls and scripted agent workflows that hardcode deprecated model identifiers will need prompt updates. Migrating these external hooks to supported models prevents unexpected execution failures during automated developer tasks.
GitHub provided dedicated assistance channels for organizations managing complex deployments across extensive engineering teams. Enterprise customers with questions or implementation concerns are instructed to contact their dedicated account managers for individualized guidance. Additionally, developers can consult platform documentation covering active models or participate in the GitHub Community forum to exchange feedback on operational experiences.
Frequently asked questions
Which GitHub Copilot models were deprecated on November 16, 2026?
GitHub deprecated Claude Opus 4.8, Claude Opus 5, and GPT-5.6 Terra across core Copilot surfaces following an advance notice published on October 15, 2026.
What alternative models should developers migrate to across Copilot interfaces?
Users transitioning from Claude Opus 4.8 and Claude Opus 5 should adopt Claude Opus 5.5, while workloads built on GPT-5.6 Terra should move to either GPT-6.1 Sol or GPT-6 Luna.
Can any users continue running the deprecated Claude models?
Individual subscribers with annual GitHub Copilot plans retain access to Claude Opus 4.8, while Claude Opus 5 remains operational strictly for runtime refusal fallbacks under existing authorized access.
Do administrators have to manually configure access to the new replacement models?
Replacement models are enabled automatically for Copilot Enterprise and Business accounts under default settings, but organizations that disabled global defaults must explicitly enable them in Copilot model policies.
Sources
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