← All articles

AI · Software · Technology

GitHub to remove three models on November 16—check fixed model settings first

Seongwoo Choi · · 2 min read

GitHub to remove three models on November 16—check fixed model settings first — explanatory illustration
English article guide generated from the section headings and opening sentences. Not an actual product screenshot.

GitHub stated in its October 15 changelog that it will discontinue three Copilot models on November 16. They are Claude Opus 4.8, Claude Opus 5, and GPT-5.6 Terra. This applies to Copilot Chat, inline editing, Ask and Agent modes, and code completion. The models themselves are not disappearing; the paths for selecting them in Copilot are closing. Still, teams that have fixed the model names may see their work stop in mid-November.

1. Check which models need to be changed first

GitHub provided the following replacement models. It recommends replacing Claude Opus 4.8 and Claude Opus 5 with Claude Opus 5.5, and GPT-5.6 Terra with GPT-6.1 Sol or GPT-6 Luna. There is one exception: individual annual-plan subscribers can continue using Claude Opus 4.8. This exception does not apply to Enterprise and Business plans.

2. Have an administrator check the automatic default switch

For Enterprise and Business customers, the replacement model will be enabled automatically depending on the default model activation settings. If an administrator has disabled the global default, the replacement model must be enabled manually under the model policy in Copilot settings. Users will see the new model in the model picker in Copilot Chat. GitHub wrote that no separate removal work is needed after the discontinuation.

3. Three-point checklist

First, find places where model names are fixed in organization policies and personal settings. If Opus 5 or Terra appears in team documents, IDE settings, or internal guides, change it before November 16. Second, run an actual task once with the replacement model. Even with the same prompt, the response length and coding style may differ. Third, check whether the change is to a model with a different cost. The GitHub notice contains no price comparison, so teams with high usage must check the pricing page separately.

4. Check model names separately against the API

Even if the same model is removed from Copilot, it may remain available through the provider's API. Therefore, Copilot settings checks and API call code checks must be performed separately. As in the Claude Sonnet 4.5 retirement article posted on the same day as this article, creating a list of model IDs currently used in API calls allows both cases to be checked at once.

Related article: Claude Sonnet 4.5 API retirement on November 30—check the model IDs currently being called first

Source: GitHub Changelog, Upcoming deprecation of selected GitHub Copilot models in mid-November (October 15, 2026)

Sources and original article

Read the Korean original on Naver

This article reflects public information available when it was written. Specifications, prices and schedules can change; check the linked official documentation.

This English edition was written and translated with AI assistance, with sources provided. For errors or additional information, please request a correction. Editorial policy