Hugin / Deadlines
The clock.
Every end date OpenAI has published, counting down.
12 upcoming13 passedSubscribe to OpenAI dates
- 25 days
OpenAI · Retirement
The v1/prompts API and reusable prompt objects shut down
Move reusable prompt content into your application code — the ledger's stated migration is inlining, not a replacement API.
Moves to: No replacement API. The page's stated migration is to "move reusable prompt content into your application code", with a linked Migrate from prompt objects guide — a path, and not a product.
Sources and checks
Announced June 3, 2026, with prompt creation de-emphasized in the platform the same day. Lands on the same date as the Agent Builder and Evals shutdowns — three products end on November 30.
Operative page re-read: Read, and it still says what this row says: 29 recorded terms present.
- 25 days
OpenAI · Retirement
The Evals dashboard and API shut down
Migrate eval workflows before the date; the ledger names Promptfoo as the documented path. Evals are already read-only from October 31.
Moves to: Promptfoo, a third-party tool: the page links "Moving from OpenAI Evals to Promptfoo for a migration path". Worth reading twice — the continuation is off-platform.
Sources and checks
The second Evals step — the October 31 read-only cliff is its own row. Graders documented for eval workflows are stated to be part of this transition; fine-tuning timelines are separate.
Operative page re-read: Read, and it still says what this row says: 29 recorded terms present.
- 25 days
OpenAI · Retirement
Agent Builder shuts down
Migrate to the Agents SDK or ChatGPT Workspace Agents — both are named on the page as the continuation path.
Moves to: The Agents SDK or ChatGPT Workspace Agents, via a linked Migrate from Agent Builder guide; ChatKit is stated to remain available.
Sources and checks
The ledger states that ChatKit remains available. The shutdown is of the builder product, not of every agent surface.
Operative page re-read: Read, and it still says what this row says: 29 recorded terms present.
- 26 days
OpenAI · Retirement
The older GPT Image models — gpt-image-1-mini, gpt-image-1.5 and the chatgpt-image-latest alias — are removed from the API
Repoint image calls at gpt-image-2, the named replacement for all three.
Moves to: gpt-image-2, named for all three ids.
Sources and checks
chatgpt-image-latest is a floating alias, so nothing in your code names a version that could warn you — the id keeps working right up to the date and then does not. Notified June 2, 2026.
Operative page re-read: Read, and it still says what this row says: 29 recorded terms present.
- 36 days
OpenAI · Retirement
The first-generation GPT-5 snapshots — gpt-5, gpt-5-mini, gpt-5-nano and gpt-5-pro — and the o3 and o3-pro reasoning models are removed from the API
Repoint at the named substitutes: gpt-5.6-sol for gpt-5, gpt-5-pro, o3 and o3-pro (pro via reasoning.mode), gpt-5.6-terra for gpt-5-mini, gpt-5.6-luna for gpt-5-nano.
Moves to: gpt-5.6-sol, -terra or -luna per snapshot; the two pro models map to gpt-5.6-sol with reasoning.mode: pro.
Sources and checks
Announced June 11, 2026. Sixteen months after GPT-5's release, its launch snapshots retire — every id in this group is snapshot-dated, so a pinned snapshot fails on the date while a floating alias will already have moved.
Operative page re-read: Read, and it still says what this row says: 29 recorded terms present.
- 36 days
OpenAI · Retirement
Custom GPTs retire across ChatGPT plans — GPTs and their GPT pages become inaccessible
If you built a custom GPT, migrate it to a plugin and test it before December 11, and rebuild any custom actions — they do not transfer. If you rely on someone else's GPT, check for the creator's replacement; permission to use a GPT does not give you permission to migrate it.
Moves to: Plugins: the FAQ's migration turns a GPT's instructions into a skill within a new plugin and copies its knowledge files. Custom actions, past conversations, sharing settings and the selected model do not carry over.
Sources and checks
Scheduled, not executed. 'The transition affects all ChatGPT plans', but Enterprise workspaces with an approved deferral retire on February 11, 2027 instead, and the FAQ tells every reader to follow the notice for their own account or workspace. The FAQ is served by a host that refuses this desk's client intermittently.
Operative page re-read: Read, and it still says what this row says: 10 recorded terms present.
- 62 days
OpenAI · Rule due
Active existing customers can no longer create new self-serve fine-tuning jobs
If a fine-tuned model is part of your roadmap, the job has to exist before this date — creation ends, not inference.
Sources and checks
Scoped to CREATING jobs. The ledger states that inference on already fine-tuned models is disabled only when the underlying base model is deprecated, which is a separate date per base model.
Operative page re-read: Read, and it still says what this row says: 29 recorded terms present.
- 62 days
OpenAI · Retirement
Four text-to-speech models are removed from the API — tts-1, tts-1-hd, gpt-4o-mini-tts-2025-03-20 and gpt-4o-mini-tts-2025-12-15
If you synthesise speech through tts-1, tts-1-hd or either dated gpt-4o-mini-tts snapshot, repoint at gpt-realtime-2.1-mini and retest before January 6. The section's own instruction is to 'See the Realtime API guide to plan your migration', so treat it as a migration to plan rather than a model id to swap.
Moves to: gpt-realtime-2.1-mini, named for all four ids and in the section's own migration sentence.
Sources and checks
Announced in a ledger section dated October 1, 2026, which states the removal comes 'with at least three months’ notice' — a floor rather than a figure, and the shorter of the two notice periods stated by the two sections the ledger dates October 1. tts-1 and tts-1-hd are undated family ids widely embedded as defaults rather than choices, so this is more likely to be found in a dependency than in a config. The named replacement is a realtime model rather than a speech endpoint; the ledger names it without stating the two produce comparable output, and this desk holds no OpenAI key and has not compared them.
Operative page re-read: Read, and it still says what this row says: 29 recorded terms present.
- 70 days
OpenAI · Retirement
Five dated GPT-4 series snapshots are removed from the API — gpt-4o-2024-08-06, gpt-4o-2024-11-20, gpt-4o-mini-2024-07-18, gpt-4.1-2025-04-14 and gpt-4.1-mini-2025-04-14
Search your configuration for those five exact snapshot ids and for any fine-tuned model built on them; the section states that 'Fine-tuned versions of these models follow the same shutdown schedule as their underlying base models.' The ledger names gpt-6-luna as the replacement for all of them.
Moves to: gpt-6-luna — the ledger's recommended replacement column names it for every one of the section's four rows.
Sources and checks
Announced in a ledger section dated October 14, 2026, which says developers were 'notified' that day and — unlike the two sections dated October 1 immediately below it — states NO notice period, so there is no figure here for this desk to pass on. Every id in this group is a dated snapshot rather than a floating alias, so code naming one is readable in a diff; the exposure is instead in fine-tuned models, which the section sweeps in by reference to their base models without listing a single one. All four rows name the same replacement, gpt-6-luna, for four differently sized models across two families; the ledger names a replacement and does not say it is equivalent to what it replaces, and this desk holds no OpenAI key and has not compared them. The ledger records a schedule and keeps carrying ids after their dates, so it cannot by itself confirm a shutdown happened.
Operative page re-read: Read, and it still says what this row says: 29 recorded terms present.
- 76 days
OpenAI · Retirement
Every legacy audio, realtime and transcription family is removed from the API — gpt-realtime, gpt-audio, gpt-4o-audio, gpt-4o-realtime, their mini variants, and gpt-4o-mini-transcribe
Repoint at the named replacements: gpt-realtime-2.1 and gpt-realtime-2.1-mini for realtime, gpt-audio-1.5 for every audio family, gpt-4o-mini-transcribe-2025-12-15 for transcription.
Moves to: gpt-realtime-2.1 and gpt-realtime-2.1-mini for realtime, gpt-audio-1.5 for the audio families, gpt-4o-mini-transcribe-2025-12-15 for transcription.
Sources and checks
Announced July 20, 2026. This group retires whole FAMILIES, not dated snapshots — a floating family id like gpt-realtime keeps working right up to the date with nothing in your code naming a version that could warn you, the chatgpt-image-latest trap at family scale.
Operative page re-read: Read, and it still says what this row says: 29 recorded terms present.
- 113 days
OpenAI · Retirement
The legacy transcription models are removed from the API — whisper-1, gpt-4o-transcribe, gpt-4o-mini-transcribe and gpt-4o-transcribe-diarize
Repoint at gpt-live-transcribe or gpt-transcribe, the two replacements the ledger names for all four ids.
Moves to: gpt-live-transcribe or gpt-transcribe, named for all four ids.
Sources and checks
Announced August 26, 2026, and the farthest date on the ledger — which is exactly why it is the one to write down. whisper-1 is embedded in a great deal of shipped code as a default rather than a choice, so this is more likely to be found in a dependency than in a config.
Operative page re-read: Read, and it still says what this row says: 29 recorded terms present.
- 147 days
OpenAI · Retirement
Three models are removed from the API — gpt-5.1, gpt-5.3-codex and gpt-5.4-nano
Search your configuration for the exact ids gpt-5.1, gpt-5.3-codex and gpt-5.4-nano. OpenAI's instruction is to 'Migrate to the recommended replacements before the shutdown date': gpt-6-sol for the first two, gpt-6-luna for gpt-5.4-nano.
Moves to: gpt-6-sol for both gpt-5.1 and gpt-5.3-codex, and gpt-6-luna for gpt-5.4-nano — the ledger's recommended replacement column for all three rows.
Sources and checks
Announced in a ledger section dated October 1, 2026, which states the removal comes 'with six months’ notice'. gpt-5.1 is a floating major id rather than a dated snapshot, so code naming it keeps working to the date with nothing in it that could warn you. Two of the section's three rows — gpt-5.1's and gpt-5.3-codex's — name the same recommended replacement, gpt-6-sol, for a chat model and a code model; the ledger names replacements and does not say they are equivalent to what they replace. The ledger records a schedule and keeps carrying ids after their dates, so it cannot by itself confirm a shutdown happened.
Operative page re-read: Read, and it still says what this row says: 29 recorded terms present.
Passed 13 · 8 filed · 5 not checked
- 5 days ago
OpenAI · Rule due
Existing evals on the deprecated Evals platform become read-only
This date passed and nothing is filedThe board is not claiming it happened. This desk has not checked.
Sources and checks
The first of two dated steps for the Evals platform — the shutdown itself is a separate row on November 30. Announced June 3, 2026; the ledger names Promptfoo as a migration path.
Operative page re-read: Read, and it still says what this row says: 29 recorded terms present.
- 10 days ago
OpenAI · Rule due
Affected ChatGPT Enterprise workspaces can no longer create new custom GPTs
This date passed and nothing is filedThe board is not claiming it happened. This desk has not checked.
Sources and checks
Planned, and the FAQ says the Enterprise dates 'are subject to change'. The Internet Archive's September 18 copy of the same FAQ gave September 25 for this cutoff; no release note records the change. Edits to existing, unmigrated GPTs are stated to continue after the cutoff.
Operative page re-read: Read, and it still says what this row says: 10 recorded terms present.
- 13 days ago
OpenAI · Retirement
A second legacy wave shuts down seventeen listed ids: the gpt-3.5/GPT-4-era snapshots (gpt-3.5-turbo-0125, gpt-4-0613, gpt-4-1106-preview, gpt-4-turbo, gpt-4.1-nano, gpt-4o-2024-05-13), the reasoning models o1, o1-pro, o3-mini and o4-mini, the original gpt-image-1 — and six fine-tuned lines including ft-gpt-4, ft-babbage-002 and ft-davinci-002
Moves to: Per id — gpt-5.6-terra for the 3.5 and o4-mini lines, gpt-5.6-sol for the GPT-4 and o1/o3 lines, gpt-5.6-luna for gpt-4.1-nano, gpt-image-2 for gpt-image-1.
This date passed and nothing is filedThe board is not claiming it happened. This desk has not checked.
Sources and checks
A separate group from the September wave, announced on its own date. The ledger lists each snapshot alias alongside the model name, so a pin on either form is covered. Until August 26 this row described only six of the seventeen ids; the fuller list above is what the cited section has carried since at least August 10.
Operative page re-read: Read, and it still says what this row says: 29 recorded terms present.
- 31 days ago
OpenAI · Price change
Billing begins for GPT-Rosalind (gpt-rosalind-research), the trusted-access life-sciences model
This date passed and nothing is filedThe board is not claiming it happened. This desk has not checked.
Sources and checks
Only approved organisations in the trusted-access program can use the model, so almost no reader is affected. The changelog states the rate and the start date; it does not say how usage before October 5 is treated beyond the fact that billing begins then.
Not on the watch list: This page is not on the term-watch list, so nothing here re-reads it on a schedule.
- 35 days ago
OpenAI · Retirement
gpt-5.4-cyber is removed from the API
Moves to: 'The most capable cyber model available to you.' — the ledger's replacement column since September 30. Until then it named gpt-5.6-cyber, which OpenAI's model catalog still lists.
This date passed and nothing is filedThe board is not claiming it happened. This desk has not checked.
Sources and checks
Announced in a ledger section dated September 11, 2026 — twenty days of notice, the shortest on the ledger's pending schedule. The replacement it names was rewritten from gpt-5.6-cyber to 'the most capable cyber model available to you' on or about September 30, with no changelog entry; the date stayed October 1. The ledger records a schedule; it keeps carrying ids after their date, so it cannot by itself confirm a shutdown happened.
Operative page re-read: Read, and it still says what this row says: 29 recorded terms present.
- 38 days ago
OpenAI · Retirement
Legacy snapshots gpt-3.5-turbo-instruct, babbage-002, davinci-002 and gpt-3.5-turbo-1106 shut down
Moves to: gpt-5.6-terra, named for all four ids.
Not establishable by this deskFiled as past by OpenAI's own ledger; the shutdown itself is not confirmed here. The four ids sit under 'Past deprecations' as of September 30 with the September 28 date and gpt-5.6-terra unchanged, while the section's paragraph still says access 'will be shut down'. No request was made to the models.
Read the entry that records itSources and checks
Part of a stated multi-wave retirement of older models with declining usage. A substitute model is named for every id in this group.
Operative page re-read: Read, and it still says what this row says: 29 recorded terms present.
- 42 days ago
OpenAI · Retirement
The Videos API and the entire Sora 2 model family shut down
Nothing to move to. The ledger's replacement column reads "---" for all six rows, and no migration sentence appears anywhere in the announcement. Measured 2026-09-07: these are the only six rows on the page in that condition, out of 49 with a replacement column.
Confirmed by this desk's own re-readShut down, by OpenAI's own account and by wire. The sora-2 model page now reads 'The Sora 2 models and Videos API were shut down on September 24, 2026 and are no longer available. There is no one-to-one replacement API.', and unauthenticated GET and POST /v1/videos answer 404 with an empty body — the answer this API gives a route that does not exist — while /v1/models answers 401. The ledger this row cites still lists all six rows under 'Upcoming deprecations' three days after the date, and the help centre still says the API 'will be discontinued'.
Read the entry that records itSources and checks
Covers the Videos API plus sora-2, sora-2-pro and three dated snapshots. The consumer app went earlier, on April 26, 2026; the help-centre article for it commits to deleting Sora content after a final export window it describes only conditionally.
Operative page re-read: Read, and it still says what this row says: 29 recorded terms present.
- 66 days ago
OpenAI · Retirement
GPT-5.4 and GPT-5.4 mini stop being available in Codex for users signed in with ChatGPT
Moves to: A recommended replacement model in Codex, or the same models via API-key authentication — the retirement is scoped to an access path, not to the model.
Confirmed by this desk's own re-readThe page still describes it as upcoming. Read 2026-09-14: the Codex models page, since reworded, says 'GPT-5.4 and GPT-5.4 mini retire from Codex on August 31, 2026' and still offers the codex -m gpt-5.4 and codex -m gpt-5.4-mini commands. The page was not updated; whether ChatGPT sign-in access actually ended is not something it settles.
Read the entry that records itSources and checks
Scoped to an access path, not the models: both remain on the OpenAI API and in Codex sessions authenticated with an API key.
Operative page re-read: Read, and it still says what this row says: 4 recorded terms present.
- 67 days ago
OpenAI · Retirement
The official DALL·E GPT is retired in ChatGPT
Moves to: Image generation in ChatGPT itself; the notice states user-created GPTs with image generation enabled are unaffected.
Not establishable by this deskNot establishable. The ChatGPT release notes, readable on 2026-09-14 after refusing this desk's client through September 1, still carry only the notice 'On August 30, 2026, we're retiring the official DALL·E GPT in ChatGPT'; nothing after it records the retirement.
Read the entry that records itSources and checks
User-created GPTs with image generation enabled are stated to be unaffected. ChatGPT Images remains available for creating and editing.
Operative page re-read: Last recorded read contained 2 recorded terms present. Historical reading carried forward; this sweep did not re-read these terms.
- 71 days ago
OpenAI · Retirement
The Assistants API shuts down on two vendors at once — OpenAI names the Responses and Conversations APIs as the replacement, Microsoft retires Azure OpenAI Assistants the same day and names Microsoft Foundry Agents instead
Moves to: The Responses or Conversations API for direct OpenAI integrations; Azure customers are pointed at Microsoft's own path, which is a different vendor's recommendation.
Confirmed by this desk's own re-readShut down, and establishable from outside: unauthenticated, /v1/assistants returns 404 with an empty body — the same answer this API gives for a route that does not exist — while a live route still answers 401 with a JSON body. Six spaced probes across 2026-08-26 and 2026-08-27, each run with the missing-route control alongside, never moved. Microsoft's Foundry (classic) notice, future-tense on the morning of the 26th, now reads "The Assistants API is retired."
Read the entry that records itSources and checks
An API shutdown affects integrations rather than chat users, and both replacements are their vendor's own recommendation rather than this desk's advice. Added 2026-08-19: this row previously carried only the OpenAI exit, which was accurate for OpenAI's surface and silent about Azure. Microsoft's Foundry (classic) Assistants page, read the same day, states the feature "is deprecated and will be retired on August 26, 2026" and directs workloads to Microsoft Foundry Agents — https://learn.microsoft.com/en-us/azure/ai-foundry/openai/concepts/assistants?view=foundry-classic
Operative page re-read: Read, and it still says what this row says: 29 recorded terms present.
- 71 days ago
OpenAI · Retirement
OpenAI o3 is retired from ChatGPT after a stated 90-day sunset
Moves to: GPT-5.6 in ChatGPT — the release notes retire o3 into the current default rather than naming a per-model substitute.
Not establishable by this deskNot establishable. Read 2026-09-14, nineteen days after the date: the model release notes still say 'OpenAI o3 will be retired from ChatGPT on August 26, 2026', in the future tense, and no later entry records the retirement. A schedule nobody updated cannot show whether it was kept.
Read the entry that records itSources and checks
A retirement notice records that access is ending. It says nothing about the model's quality or about why.
Operative page re-read: Last recorded read contained 1 recorded term present. Historical reading carried forward; this sweep did not re-read these terms.
- 87 days ago
OpenAI · Retirement
gpt-5.2-chat-latest and gpt-5.3-chat-latest shut down on the API, replaced by gpt-5.6-sol
Moves to: gpt-5.6-sol, named in the ledger's replacement column for both aliases.
Confirmed by this desk's own re-readExecuted on schedule, 94 days after the May 8 notice. The ledger still carries both ids against "Aug 10, 2026" with gpt-5.6-sol as the replacement; neither appears on the live models list, and no "-chat-latest" alias does.
Read the entry that records itSources and checks
Scoped to the two dated chat-latest aliases. The deprecations ledger is the provider's own schedule and is where any change to this date would appear.
Operative page re-read: Read, and it still says what this row says: 29 recorded terms present.
- 88 days ago
OpenAI · Retirement
The Atlas browser stops working
Moves to: ChatGPT for browser-based agentic work, named in the article's own title.
Not establishable by this deskReported to have happened, but not establishable from any OpenAI page this desk can read: help.openai.com, openai.com and chatgpt.com all refuse or challenge the identifying client, while the developer docs serve it the whole document.
Read the entry that records itSources and checks
The release notes say Atlas is scheduled to stop working on this date. A scheduled shutdown is a stated plan, not a guarantee of the hour.
Operative page re-read: Last recorded read contained 1 recorded term present. Historical reading carried forward; this sweep did not re-read these terms.