OpenAI Confirms GPT-5.5 Survives Only via API Key After Codex Retirement
- Source
- x.com
- Date
OpenAI confirmed GPT-5.5 will retire from ChatGPT, ChatGPT Work, and default Codex on October 14. The model does not disappear entirely: it stays reachable through the API Platform, and inside Codex sessions specifically authenticated with an API key rather than a ChatGPT login. Teams that have not set up API-key authentication for Codex will lose default access to GPT-5.5 on that date and need to migrate to GPT-5.6 Sol or GPT-6 Astra instead. The distinction is a practical one for anyone running Codex in CI or in an internal tool: workflows wired to a ChatGPT session token break on October 14, while workflows already using an API key keep working with no code change beyond confirming the key stays valid. OpenAI's announcement gives about a month of lead time, which is short for teams that have not audited how their Codex integrations authenticate. The safest move is to check now, since API-key auth is the one path OpenAI is explicitly keeping open.
GPT-5.5 will remain available via the OpenAI API Platform and in Codex sessions authenticated with an API key: https://t.co/pztFmVBNHQ
Context
OpenAI says GPT-5.5 will keep working through its API platform and in Codex sessions authenticated with an API key, even as the model is retired elsewhere. According to OpenAI's retirement notice, GPT-5.5 is being pulled from ChatGPT, ChatGPT Work, and default Codex access across all plans on October 14, 2026, just under six months after it launched. Codex users who rely on the model without their own API key are told to switch to GPT-5.6 Sol or GPT-6 Astra before that date; anyone authenticating Codex with a personal API key can keep using GPT-5.5 past the cutoff.
Checking sign-in…
Loading comments…




