GitHub deprecates GPT-5.2 models

GitHub Copilot’s model picker is changing again — and this time the change comes with a hard date. On May 1, GitHub said it will deprecate GPT-5.2 a(github.blog)ce, but it matters because these models sit inside editors, chats, inline edits, and automation flows teams already depend on. When a model disappears, prompts, outputs, latency, and cost can all shift at once. (github.blog) ### What exactly is going away? GitHub says GPT-5.2 and GPT-5.2-Codex will be removed across Cop(github.blog)2-Codex stays available in Copilot Code Review, at least for now. GitHub also published the replacement path in the same notice — GPT-5.2 users should move to GPT-5.5, and GPT-5.2-Codex users should move to GPT-5.3-Codex. (github.blog) ### Why is the Code Review exception interesting? Because it shows this is not a blanket “old model out, new model in” swap. GitHub is still keepi(github.blog)he company thinks the model still has a useful fit for a specific workflow, or that migrating that workflow cleanly takes longer than changing the general picker. Either way, platform teams should read the exception as a warning — product surfaces can diverge even inside the same vendor. (github.blog) ### Is this just a normal refresh(github.blog)5 and GPT-5-Codex in February and pointed users to GPT-5.2 and GPT-5.2-Codex. Now, less than three months later, GitHub is moving again, this time toward GPT-5.5 and GPT-5.3-Codex. Basically, the “supported model” list is behaving more like a live cloud service than a fixed platform dependency. (github.blog) ### Why now? The timing lines up with GitHub’s bigger pricing reset. Five days before this deprecation notice, GitHub said all Copilo(github.blog)counting for input, output, and cached tokens. If billing is becoming more granular, GitHub has a stronger reason to steer users toward the models it wants to support operationally and economically. (github.blog) ### What changes for developers day to day? If you manually picked GPT-5.2 or GPT-5.2-Codex, you need to switch before June 1. (github.blog)That means the same prompt may start hitting a different model without a dramatic UI moment — a bit like keeping the same app shortcut while the engine under the hood gets swapped. (docs.github.com) ### What should platform teams do with this? Treat model choice as configuration, not as a permanent product feature. Pin where you can, test fallback models before deadlines(github.blog)pilot sits inside internal developer workflows, because a model migration can hit quality and cost at the same time. (github.blog) ### Does this signal anything bigger? Yes. Copilot is moving toward a world where model availability, billing, and feature behavior are tightly linked. GitHub’s docs already say supported models v(docs.github.com)y is not just that GPT-5.2 is leaving — it’s that model lifecycle management is now part of normal software operations. (docs.github.com) ### Bottom line? GitHub did not just trim a menu. It set a June 1 deadline, named the replacement models, and tied the change to a broader shift in how Copilot gets pri(github.blog) layer is movable, and design workflows that survive the move. (github.blog)