OpenAI retires GPT-5.5 from ChatGPT and Codex on October 14
Five weeks to move Codex and ChatGPT workflows to the GPT-5.6 family; hardcoded 5.5 calls will error, though direct API keys keep working for now.
Copy markdown
The cutoff: October 14, and it fails loud
OpenAI is pulling GPT-5.5 from ChatGPT, ChatGPT Work, and Codex on Oct 14, 2026 — about five weeks out. Requests that name 5.5 will error rather than fall back, so anything with the model hardcoded breaks the moment it's gone.
Meet your replacements: Sol, Terra, Luna
The GPT-5.6 family takes over: Sol for heavy reasoning on large codebases ($5/$30 per million tokens in/out), Terra as the balanced default ($2.50/$15), and Luna for cheap, fast jobs ($1/$6). GPT-6 Astra is the other landing spot OpenAI points to.
What you actually have to change
Update every place a model name is saved: Codex CLI scripts, workspace defaults, custom agents, scheduled tasks, and managed configs. OpenAI’s documented swap is gpt-5.4 → gpt-5.6-terra and gpt-5.4-mini → gpt-5.6-luna wherever they appear.
Your API keys aren't in the blast radius
The retirement hits the ChatGPT-account surfaces, not the standalone API — calls authenticated with an API key keep working for now. But if you drive Codex through a ChatGPT subscription, you’re on the clock like everyone else.
Builders are asking OpenAI to keep 5.5
On OpenAI’s developer forum, Codex Pro users are pushing back, calling 5.5 “fast, consistent, and dependable” and saying GPT-5.6 over-reasons and expands scope — more compute for the same result. They want a legacy option and 90-day retirement notices.
Elsewhere: gpt-5.4-cyber retires even sooner
If you use OpenAI’s cyber-tuned model, mark Oct 1: gpt-5.4-cyber is being deprecated in favor of gpt-5.6-cyber, two weeks ahead of the GPT-5.5 sunset. Same drill — repoint any hardcoded name before the date.