🟡 🤖 Models Saturday, May 2, 2026 · 2 min read ·

GitHub is retiring GPT-5.2 and GPT-5.2-Codex from Copilot on June 1, 2026 — migration to GPT-5.5 and GPT-5.3-Codex

Editorial illustration: GitHub Copilot dashboard s novim modelom koji zamjenjuje stari

GitHub announces the retirement of GPT-5.2 and GPT-5.2-Codex from all Copilot experiences on June 1, 2026. Chat, inline edit, ask and agent mode, and code completion users will move to GPT-5.5, while Codex users will move to GPT-5.3-Codex. The exception is Copilot Code Review, where GPT-5.2-Codex remains available. Enterprise administrators must manually enable the new models in model policies before the deadline.

GitHub has announced plans to retire two models from the GitHub Copilot ecosystem — GPT-5.2 and GPT-5.2-Codex — with a deadline of June 1, 2026. The announcement provides a concrete migration path and requires explicit action from enterprise administrators before the deadline.

Which products are affected?

The retirement covers Copilot Chat, inline edits, ask and agent modes, and code completion — in other words, all productive experiences where users choose a model for interaction. The only exception is Copilot Code Review, where GPT-5.2-Codex remains available after the deadline. This exception reflects GitHub’s decision to keep the specific Codex signature in the review workflow stable while other experiences are unified on the newer generation.

What is the migration path?

The mapping is straightforward:

  • GPT-5.2 → GPT-5.5 (all Chat and agent functionality)
  • GPT-5.2-Codex → GPT-5.3-Codex (Codex-specific workflow)

GPT-5.5 is intended as the default for general Copilot tasks, while GPT-5.3-Codex retains code-specific reasoning capabilities optimized for inline editing and agent mode. GitHub notes that after the retirement no action is required to remove the old models — they will simply disappear from the selector.

How should enterprise administrators respond?

Enterprise users face a concrete action item. Administrators must manually enable access to the replacement models via model policies in Copilot settings. Without this action, users will not have GPT-5.5 or GPT-5.3-Codex in the selector when the old models are retired — and could be left without a functional choice.

After enabling, it is recommended to verify at the individual user settings level and confirm model availability in the Copilot Chat selector in VS Code and github.com. Enterprise users with additional questions are directed to their account managers.

This announcement is an example of GitHub’s planned migration cycle that accelerated during 2026: new Copilot models arrive on a quarterly cadence, and old ones are systematically retired 6–9 months after the newer iteration takes effect. The predictable cadence gives administrators time for regression testing and policy review before new models become the mandatory default.

Frequently Asked Questions

What is the exact retirement date?
June 1, 2026. GPT-5.2 and GPT-5.2-Codex will be shut down in Copilot Chat, inline edits, ask and agent modes, and code completion on that date.
What is the migration path?
GPT-5.2 → GPT-5.5 for all general Copilot tasks. GPT-5.2-Codex → GPT-5.3-Codex for Codex users. Exception: GPT-5.2-Codex remains available in Copilot Code Review.
What do enterprise administrators need to do?
Enable access to the replacement models through model policies in Copilot settings before June 1, and confirm the models appear in the Copilot Chat selector in VS Code and github.com. No action is required to remove deprecated models after the deadline.
🤖

This article was generated using artificial intelligence from primary sources.