← Dev digest

Copilot model retirement: scope, alternatives and code-review exception

The news at the time

GitHub announced GPT-5.2 and GPT-5.2-Codex deprecation on 2026-06-05 across most Copilot experiences, while explicitly retaining GPT-5.2 for Copilot code review in that announcement. This does not establish retirement across other providers or APIs.

The announcement suggests GPT-5.5 for GPT-5.2 and GPT-5.3-Codex for GPT-5.2-Codex. Enterprise administrators may need to enable alternatives through model policies before users can select them.

Follow-up checked during renewal

No additional follow-up fact was established in this renewal. This does not establish that nothing changed.

What to review before applying this

Check the specific Copilot product and organization policy before migrating. These are the historical notice’s exceptions and alternatives, not a claim that its model availability remains unchanged today.

Editorial review suggestions; no hands-on product experiment was performed.

Read the original reporting ↗

Claim-by-claim source evidence

GitHub announced GPT-5.2 and GPT-5.2-Codex deprecation on 2026-06-05 across most Copilot experiences, while explicitly retaining GPT-5.2 for Copilot code review in that announcement. This does not establish retirement across other providers or APIs.

Note that GPT-5.2 is still available as part of Copilot code review.

Evidence source ↗

As of today, June 5, 2026, we have deprecated the following models across most GitHub Copilot experiences

Evidence source ↗

The announcement suggests GPT-5.5 for GPT-5.2 and GPT-5.3-Codex for GPT-5.2-Codex. Enterprise administrators may need to enable alternatives through model policies before users can select them.

Copilot Enterprise administrators may need to enable access to alternative models through their model policies in Copilot settings.

Evidence source ↗

GPT-5.2 2026-06-05 GPT-5.5 GPT-5.2-Codex 2026-06-05 GPT-5.3-Codex

Evidence source ↗

Korean digest for the historical date: 2026-06-07. Quotations and source context were reviewed editorially; this is not an independent experimental verification.

Discussion