Per OpenAI's model docs, GPT-5.5 retires from ChatGPT, ChatGPT Work and Codex on all plans on 2026-10-14; the OpenAI API is not affected. Codex users on ChatGPT sign-in should pick gpt-6-sol (Plus, Pro, Business, Enterprise, Edu) or gpt-6-luna in the desktop app (Free, Go), with gpt-6.1-sol recommended for complex coding. Any config.toml, custom agent, scheduled task or script pinned to gpt-5.5 needs updating now.
Key Takeaways
- ✓Effective 2026-10-14: GPT-5.5 leaves ChatGPT, ChatGPT Work and Codex on every plan; the OpenAI API is unaffected
- ✓Replacements:
gpt-6-solfor Plus/Pro/Business/Enterprise/Edu,gpt-6-lunain the desktop app for Free/Go (both 'when available') - ✓For complex coding OpenAI recommends
gpt-6.1-sol, near-Astra at 1/5 of Astra's standard price per OpenAI - ✓Check 4 places:
modelinconfig.toml,codex exec -m, custom agents, scheduled tasks and scripts - ✓Enterprise/Edu admins must enable newer models first; GPT-5.6 Sol/Terra/Luna remain available during the rollout
Key Decision Metrics at a Glance
Turn your technical choice into a development budget
Compare 40 dev plans & simulate token costs vs $20/mo subscriptions
Project Links & Resources
Direct AccessIn-Depth Technical Analysis
OpenAI's Codex model documentation states that GPT-5.5 retires from ChatGPT, ChatGPT Work and Codex on all plans, including Business, Enterprise and Edu, on October 14, 2026. The retirement does not apply to the OpenAI API. Codex users on ChatGPT sign-in should choose GPT-6 Sol (gpt-6-sol) on Plus, Pro, Business, Enterprise and Edu, or GPT-6 Luna (gpt-6-luna) in the desktop app on Free and Go, both 'when available'. For complex coding and agentic work the docs recommend GPT-6.1 Sol, which OpenAI positions as near GPT-6 Astra at one-fifth of Astra's standard price. In Enterprise and Edu, newer models are off until an admin enables them, and choosing a model locally does not grant access. GPT-5.6 Sol, Terra and Luna stay available during the rollout. The practical risk is unattended configuration: search for gpt-5.5 in config.toml, codex exec -m invocations, custom agents and scheduled tasks, switch to gpt-6.1-sol or the plan-appropriate replacement, and move anything that truly depends on GPT-5.5 to the API while you regression-test.
Benchmark side-by-side against alternatives, or calculate monthly token cost vs subscription break-even.
Discussion & Comments
0Sign in to join the discussion
Connect with AI developers to exchange benchmark insights.