OpenAI is retiring GPT-5.5 from ChatGPT, ChatGPT Work, and Codex on October 14, 2026, across all plans (consumer through Enterprise/Edu), directing Codex users on ChatGPT sign-in to switch to GPT-5.6 Sol, with GPT-6 Astra as the alternative — and per OpenAI's own developer LinkedIn post plus third-party write-ups quoting OpenAI's ChatGPT models documentation, the retirement does not apply to the OpenAI API, where GPT-5.5 remains available. This fits a documented cadence: OpenAI's release notes show ChatGPT-side retirements of GPT-4o and legacy models (Feb 2026) and GPT-5.2 (June 2026) with the API unchanged, under a stated policy of removing models ~90 days after a successor lands, and the GPT-6 family (Astra, then Sol and Luna on Sept 22, GPT-6.1 Sol on Sept 29) is the incoming generation. Two wrinkles worth flagging: the originally echoed X quote ('switching to GPT-6 Astra') was a paraphrase — official guidance names GPT-5.6 Sol first — and the October 14 date and scope are now confirmed via OpenAI's LinkedIn account and quoted doc screenshots rather than the deprecations page the case was watching; community mood is churn-weary (one commenter: after the overnight GPT-4o removal, 'nobody gives a fuck what it does anymore'), and no documented mapping exists for which GPT-5.5 ChatGPT tier maps to which successor.
OpenAI is executing the exact ~90-day-successor deprecation cadence Scott's Model Perishability canon (ip:concept.model-perishability) already holds, and the confirmation landed on the case's own pre-registered cool branch: GPT-5.5 dies Oct 14 on ChatGPT/Work/Codex subscription surfaces only, with the API — the lane his LiteLLM gateway and paid account actually ride — explicitly carved out, so this is his standing position vindicated again, not a new claim or a workflow-changing event. The only concrete bearings are cheap, discipline-shaped checks before Oct 14: whether any Codex CLI invocations pin gpt-5.5 via ChatGPT sign-in, and whether the deprecations page's reported no-replacement TTS retirement (unverified beyond one HN quote) touches his OpenAI TTS usage.
ip:concept.model-perishabilitydev:technology.codex-clidev:technology.openaidev:technology.litellmradar:anthropic-sonnet-45-deprecationradar:github-copilot-model-deprecationsradar:openai-custom-gpt-plugin-migrationradar:openai-astra-silent-rerouting-claim
queries asked of Scott's wikis
- model perishability swappable model dependencies
- LiteLLM gateway model routing fallback config
- Codex ChatGPT sign-in vs API key workflow
- hardcoded model IDs in agent harnesses
- prompt cache free writes model economics
- OpenAI deprecation cadence 90-day successor policy
now 0 pts/hpeak 3 pts/hcomments 0/hpeers p14momentum: steady3 platformsage 619h
points/hour across evidence · reading as of 2026-10-12 02:59:37.977291+11:00 · deterministic, not a model opinion
2026-10-02T18:42:51Z
grounded: known/low — OpenAI is executing the exact ~90-day-successor deprecation cadence Scott's Model Perishability canon (ip:concept.model-perishability) already holds, and the co
2026-10-02T18:34:31Z
The case's meaning shifts from circulating quote to a date-bound verification watch: OpenAI's official deprecations page is now in evidence and confirms an active, aggressive deprecation program (TTS models retired with no adequate replacement), but no quoted content yet lists GPT-5.5, confirms the October 14 date, or pins ChatGPT-vs-API/Codex scope. With the claimed date ~11 days out, the decisive next fact is whether the page codifies GPT-5.5's retirement; community engagement itself has gone quiet (0.33 pts/h, near-zero HN traction), so the low heat reflects a sleepy story, not a settled one.
2026-10-02T17:39:07Z
evidence attached: hn.story.49935647 — OpenAI's official deprecations page is exactly where the GPT-5.5 retirement scope and schedule the case awaits would be codified.
2026-09-21T15:46:11Z
The new HN item adds a Codex-specific framing and a user claim about GPT-5.5’s assistant-like behavior, but provides no source, implementation result, or independent confirmation of retirement scope. It does not substantiate the prior attachment’s claim that workflow migration is being forced.
2026-09-21T13:22:11Z
evidence attached: hn.story.49786558 — Directly corroborates the existing case about OpenAI retiring GPT-5.5/Codex behavior and forcing workflow migration.
2026-09-20T06:28:50Z
The HN title introduces October 14 as a claimed retirement date, making the report more specific but not independently verified: no linked announcement or supporting reporting is supplied. This is a verification lead, not yet a migration deadline for Scott, and the sparse cross-platform pickup does not warrant higher attention.
2026-09-20T06:21:42Z
evidence attached: hn.story.49772909 — This independent report corroborates the existing GPT-5.5 retirement episode and supplies a concrete October 14 date.
2026-09-16T10:27:03Z
The discussion adds anecdotes about GPT-5.5's usefulness and an unsupported cache-pricing claim, not confirmation of retirement or demonstrated migration costs. This remains an unverified lifecycle report rather than an actionable change to Scott's workflows.
2026-09-15T22:37:17Z
The added post shows user concern about the reported retirement, not independent verification or an observed migration impact. The earlier characterization as an owner statement was too strong: the announcement remains reconstructed testimony, with no established deadline or affected access surface.
2026-09-15T22:21:44Z
evidence attached: reddit.post.1whe0n4 — This user report independently reflects the announced GPT-5.5 retirement and the resulting model-migration impact.
2026-09-15T21:59:04Z
grounded: known/low — At present this is only a possible instance of Scott’s already-held Model Perishability position: model dependencies should be swappable and re-evaluated, as su
2026-09-15T21:54:05Z
case created — The linked owner statement describes a distinct lifecycle change rather than new evidence about Astra's release capabilities.