GPT-5.2 and GPT-5.2-Codex Deprecated From GitHub Copilot: June 2026 Migration Guide
GitHub Copilot deprecates GPT-5.2 and GPT-5.2-Codex across most experiences as of June 5, 2026. Three migration waves converge through July 23. GPT-5.3-Codex becomes LTS at 6x multiplier.
2026年6月9日 · 阅读约 6 分钟
Key Takeaways
As of June 5, 2026, GPT-5.2 and GPT-5.2-Codex have been deprecated across most GitHub Copilot experiences. This marks the first wave of a three-phase model retirement that will culminate on July 23, 2026, when every legacy Codex API model older than GPT-5.3-Codex is permanently shut down. Here is what changes and how to migrate:
- Copilot deprecation (June 5): GPT-5.2 and GPT-5.2-Codex removed from Copilot Chat, inline edits, agent mode, and completions. GPT-5.2 remains available for Copilot Code Review.
- Codex sunset (June 2): GPT-5.2 and GPT-5.3-Codex removed from OpenAI Codex for ChatGPT account users. Five days notice.
- API shutdown (July 23): Every remaining legacy Codex API model ID will stop working permanently.
- GPT-5.3-Codex is the LTS replacement: Available through February 4, 2027 for Copilot Business and Enterprise. However, its multiplier jumps from 1x to 6x on the premium request table.
Background: Three Waves of Model Retirements
The June 2026 model deprecation cycle is not a single event — it is three converging retirement waves from two different platforms, affecting teams that rely on Copilot, Codex, or both.
Wave 1: OpenAI Codex Sunset (June 2)
On May 27, 2026, OpenAI announced via a single tweet that GPT-5.2 and GPT-5.3-Codex would be sunset from Codex on June 2 for users logged in with a ChatGPT account. The stated reason was "to simplify our Codex compute fleet management." For free plan users, GPT-5.5 became the default frontier model.
This was notably short notice — just five calendar days — and triggered a wave of frustration on the OpenAI Community forum. Multiple developers reported that their agentic coding workflows broke mid-sprint, with no clear migration path provided by OpenAI at the time of announcement.
Wave 2: GitHub Copilot Deprecation (June 5)
GitHub followed on June 5 by deprecating GPT-5.2 and GPT-5.2-Codex across most Copilot experiences — including Copilot Chat, inline edits, ask and agent modes, and code completions. The only exception is Copilot Code Review, where GPT-5.2 remains available for an unspecified transition period.
This deprecation was better telegraphed. GitHub originally announced the plan on May 1 with a June 1 target date, later pushed to June 5. The recommended replacements are GPT-5.5 (for GPT-5.2) and GPT-5.3-Codex (for GPT-5.2-Codex).
Wave 3: OpenAI API Shutdown (July 23)
The final and most consequential wave hits on July 23, 2026. Every legacy Codex API model ID older than GPT-5.3-Codex will be permanently decommissioned. After this date, any CI pipeline, config.toml, or Agents SDK orchestrator referencing these model strings will fail with a 404:
gpt-5.2-codexcodex-mini-latest(already removed from API on February 12)- Other legacy Codex model strings
| Wave | Date | Platform | Affected Models | Replacement | Notice Period |
|---|---|---|---|---|---|
| Codex Sunset | June 2 | OpenAI Codex | GPT-5.2, GPT-5.3-Codex | GPT-5.5 (free) / GPT-5.3-Codex (Pro) | 5 days |
| Copilot Deprecation | June 5 | GitHub Copilot | GPT-5.2, GPT-5.2-Codex | GPT-5.5 / GPT-5.3-Codex | 35 days |
| API Shutdown | July 23 | OpenAI API | All legacy Codex models | GPT-5.3-Codex or newer | ~60 days |
The GPT-5.3-Codex LTS Commitment and Its Price
GPT-5.3-Codex was designated a Long-Term Support (LTS) model on March 18, 2026, guaranteeing availability through February 4, 2027 for Copilot Business and Enterprise users. On May 17, it became the default base model for all Business and Enterprise organizations.
However, the transition comes with a significant cost change. In GitHub Copilot's updated premium request multiplier table (effective June 1, 2026), GPT-5.3-Codex jumped from 1x to 6x. For teams that have been running agentic coding sessions on GPT-5.3-Codex at the old 1x multiplier, the effective cost increase is 6-fold overnight.
| Model | Old Multiplier | New Multiplier | Change |
|---|---|---|---|
| GPT-5.3-Codex | 1x | 6x | +500% |
| GPT-5.5 | n/a (new) | 7.5x | — (new model) |
| Claude Opus 4.7 | 7.5x | 27x | +260% |
Source: GitHub Copilot Plans & Pricing, MindStudio multiplier analysis
For reference, the MindStudio analysis notes that "if you're a Copilot subscriber who has been running agentic coding sessions on frontier models, your effective cost is about to increase by a factor of 3.6 to 6 depending on which model you've been leaning on" source.
Developer Community Reaction
The rapid deprecation cycle has generated significant discussion across Reddit and HN. Key themes:
Frustration with short notice periods. OpenAI's 5-day notice for the Codex sunset on June 2 drew sharp criticism. One developer on the OpenAI forum wrote: "With the removal of GPT-5.3-Codex, the main value proposition that brought me to the platform is unfortunately gone."
Cost anxiety from multiplier changes. The GitHub Copilot subreddit has active threads discussing the GPT-5.5 multiplier of 7.5x and the GPT-5.3-Codex jump from 1x to 6x. Multiple users noted that Copilot Pro's "unlimited" premium requests now consume substantially more quota for the same agentic workflows.
Migration confusion. Developers working across both Copilot and Codex face separate migration paths for each platform, with different deadlines and different recommended replacements. Teams using the Codes API directly or via orchestrators like LangGraph or n8n must update model strings across multiple systems before July 23.
Practical Migration Checklist
For Copilot users, the migration is largely automatic for GUI-based usage. The key manual actions are for custom configurations and pipeline integrations.
- Update
config.tomlor.copilotconfigreferences fromgpt-5.2-codextogpt-5.3-codex - Check CI/CD pipelines for hardcoded Codex model IDs — update before July 23
- Verify model access: Copilot Enterprise admins may need to enable GPT-5.3-Codex in organization settings
- Audit premium request budgets: at 6x multiplier, agentic workflows consume significantly more quota
- For Codex CLI users on ChatGPT accounts: GPT-5.5 is now the default — test workflows against it
- Consider locking to GPT-5.3-Codex where available (LTS through Feb 2027) for stability in production
# Example: Verify available models in Copilot CLI
copilot config --list-models
# Expected output should include gpt-5.3-codex and gpt-5.5
# If old model IDs still return errors, update your configWhat This Means for Developers
The June 2026 model deprecation cycle sends a clear signal: the era of cheap Codex-family inference on Copilot is ending. As OpenAI consolidates its model lineup around GPT-5.5, and GitHub re-prices frontier models with higher multipliers, teams must budget more aggressively for AI coding costs.
For developers relying on agentic coding (Claude Code, Cursor, Copilot agent mode), the cost-per-task is rising across the board — not just on the Copilot side. The combination of model retirements and multiplier increases creates a "tax" on AI-assisted development that teams should bake into their 2026 planning.
Whether you use GitHub Copilot, OpenAI Codex, or both, the migration window is clear: update your model references before July 23, and plan for the new multiplier pricing.

Further Reading
- GitHub Changelog: GPT-5.2 and GPT-5.2-Codex deprecated
- OpenAI Community: GPT-5.2 sunset announcement
- GitHub Copilot Plans & Pricing
- The Codex Model Sunset: June-July 2026 Deprecation Timeline
- GPT-5.3-Codex Is Now the Copilot Default
Tool Mentions
This article references OpenAI, GitHub Copilot, Claude Code, Cursor, n8n, and LangGraph — all AI coding tools affected by the ongoing model consolidation trend.