BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//Hugin//Provider deadline board//EN
CALSCALE:GREGORIAN
METHOD:PUBLISH
X-WR-CALNAME:Hugin — OpenAI deadlines
X-WR-CALDESC:Published end dates from OpenAI tracked by Hugin. This subscri
 ption contains only OpenAI dates\; it does not imply any unpublished or in
 ferred term.
X-PUBLISHED-TTL:PT12H
REFRESH-INTERVAL;VALUE=DURATION:PT12H
BEGIN:VEVENT
UID:openai-reusable-prompts-shutdown@hugin.studio
DTSTAMP:20261106T025252Z
SEQUENCE:235
DTSTART;VALUE=DATE:20261130
DTEND;VALUE=DATE:20261201
SUMMARY:⚑ OpenAI: The v1/prompts API and reusable prompt objects shut dow
 n
DESCRIPTION:The v1/prompts API and reusable prompt objects shut down\n\nMOV
 ES TO: No replacement API. The page's stated migration is to "move reusabl
 e prompt content into your application code"\, with a linked Migrate from 
 prompt objects guide — a path\, and not a product.\n\nBEFORE THIS DATE: 
 Move reusable prompt content into your application code — the ledger's s
 tated migration is inlining\, not a replacement API.\n\nCaveat: Announced 
 June 3\, 2026\, with prompt creation de-emphasized in the platform the sam
 e day. Lands on the same date as the Agent Builder and Evals shutdowns —
  three products end on November 30.\n\nAuthoritative document (API depreca
 tions ledger): https://developers.openai.com/api/docs/deprecations\n\nTrac
 ked by Hugin: https://hugin.studio/deadlines?provider=OpenAI\nOnly dates a
  provider has published about its own product appear here.
URL:https://hugin.studio/deadlines?provider=OpenAI
CATEGORIES:OpenAI\,retirement
TRANSP:TRANSPARENT
STATUS:TENTATIVE
BEGIN:VALARM
ACTION:DISPLAY
DESCRIPTION:OpenAI: Move reusable prompt content into your application code
  — the ledger's stated migration is inlining\, not a replacement API.
TRIGGER:-P7D
END:VALARM
END:VEVENT
BEGIN:VEVENT
UID:openai-evals-shutdown@hugin.studio
DTSTAMP:20261106T025252Z
SEQUENCE:235
DTSTART;VALUE=DATE:20261130
DTEND;VALUE=DATE:20261201
SUMMARY:⚑ OpenAI: The Evals dashboard and API shut down
DESCRIPTION:The Evals dashboard and API shut down\n\nMOVES 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-pla
 tform.\n\nBEFORE THIS DATE: Migrate eval workflows before the date\; the l
 edger names Promptfoo as the documented path. Evals are already read-only 
 from October 31.\n\nCaveat: The second Evals step — the October 31 read-
 only cliff is its own row. Graders documented for eval workflows are state
 d to be part of this transition\; fine-tuning timelines are separate.\n\nA
 uthoritative document (API deprecations ledger): https://developers.openai
 .com/api/docs/deprecations\n\nTracked by Hugin: https://hugin.studio/deadl
 ines?provider=OpenAI\nOnly dates a provider has published about its own pr
 oduct appear here.
URL:https://hugin.studio/deadlines?provider=OpenAI
CATEGORIES:OpenAI\,retirement
TRANSP:TRANSPARENT
STATUS:TENTATIVE
BEGIN:VALARM
ACTION:DISPLAY
DESCRIPTION:OpenAI: Migrate eval workflows before the date\; the ledger nam
 es Promptfoo as the documented path. Evals are already read-only from Octo
 ber 31.
TRIGGER:-P7D
END:VALARM
END:VEVENT
BEGIN:VEVENT
UID:openai-agent-builder-shutdown@hugin.studio
DTSTAMP:20261106T025252Z
SEQUENCE:235
DTSTART;VALUE=DATE:20261130
DTEND;VALUE=DATE:20261201
SUMMARY:⚑ OpenAI: Agent Builder shuts down
DESCRIPTION:Agent Builder shuts down\n\nMOVES TO: The Agents SDK or ChatGPT
  Workspace Agents\, via a linked Migrate from Agent Builder guide\; ChatKi
 t is stated to remain available.\n\nBEFORE THIS DATE: Migrate to the Agent
 s SDK or ChatGPT Workspace Agents — both are named on the page as the co
 ntinuation path.\n\nCaveat: The ledger states that ChatKit remains availab
 le. The shutdown is of the builder product\, not of every agent surface.\n
 \nAuthoritative document (API deprecations ledger): https://developers.ope
 nai.com/api/docs/deprecations\n\nTracked by Hugin: https://hugin.studio/de
 adlines?provider=OpenAI\nOnly dates a provider has published about its own
  product appear here.
URL:https://hugin.studio/deadlines?provider=OpenAI
CATEGORIES:OpenAI\,retirement
TRANSP:TRANSPARENT
STATUS:TENTATIVE
BEGIN:VALARM
ACTION:DISPLAY
DESCRIPTION:OpenAI: Migrate to the Agents SDK or ChatGPT Workspace Agents 
 — both are named on the page as the continuation path.
TRIGGER:-P7D
END:VALARM
END:VEVENT
BEGIN:VEVENT
UID:openai-gpt-image-legacy-shutdown@hugin.studio
DTSTAMP:20261106T025252Z
SEQUENCE:15
DTSTART;VALUE=DATE:20261201
DTEND;VALUE=DATE:20261202
SUMMARY:⚑ OpenAI: The older GPT Image models — gpt-image-1-mini\, gpt-i
 mage-1.5 and the chatgpt-image-latest alias — are removed from the API
DESCRIPTION:The older GPT Image models — gpt-image-1-mini\, gpt-image-1.5
  and the chatgpt-image-latest alias — are removed from the API\n\nMOVES 
 TO: gpt-image-2\, named for all three ids.\n\nBEFORE THIS DATE: Repoint im
 age calls at gpt-image-2\, the named replacement for all three.\n\nCaveat:
  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 dat
 e and then does not. Notified June 2\, 2026.\n\nAuthoritative document (AP
 I deprecations ledger): https://developers.openai.com/api/docs/deprecation
 s\n\nTracked by Hugin: https://hugin.studio/deadlines?provider=OpenAI\nOnl
 y dates a provider has published about its own product appear here.
URL:https://hugin.studio/deadlines?provider=OpenAI
CATEGORIES:OpenAI\,retirement
TRANSP:TRANSPARENT
STATUS:TENTATIVE
BEGIN:VALARM
ACTION:DISPLAY
DESCRIPTION:OpenAI: Repoint image calls at gpt-image-2\, the named replacem
 ent for all three.
TRIGGER:-P7D
END:VALARM
END:VEVENT
BEGIN:VEVENT
UID:openai-gpt5-o3-snapshots-shutdown@hugin.studio
DTSTAMP:20261106T025252Z
SEQUENCE:46
DTSTART;VALUE=DATE:20261211
DTEND;VALUE=DATE:20261212
SUMMARY:⚑ OpenAI: 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
DESCRIPTION:The first-generation GPT-5 snapshots — gpt-5\, gpt-5-mini\, g
 pt-5-nano and gpt-5-pro — and the o3 and o3-pro reasoning models are rem
 oved from the API\n\nMOVES TO: gpt-5.6-sol\, -terra or -luna per snapshot\
 ; the two pro models map to gpt-5.6-sol with reasoning.mode: pro.\n\nBEFOR
 E THIS DATE: 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.\n\nCaveat: Announced June 11\, 2026. S
 ixteen months after GPT-5's release\, its launch snapshots retire — ever
 y id in this group is snapshot-dated\, so a pinned snapshot fails on the d
 ate while a floating alias will already have moved.\n\nAuthoritative docum
 ent (API deprecations ledger): https://developers.openai.com/api/docs/depr
 ecations\n\nTracked by Hugin: https://hugin.studio/deadlines?provider=Open
 AI\nOnly dates a provider has published about its own product appear here.
URL:https://hugin.studio/deadlines?provider=OpenAI
CATEGORIES:OpenAI\,retirement
TRANSP:TRANSPARENT
STATUS:TENTATIVE
BEGIN:VALARM
ACTION:DISPLAY
DESCRIPTION:OpenAI: 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.
TRIGGER:-P7D
END:VALARM
END:VEVENT
BEGIN:VEVENT
UID:openai-custom-gpts-retirement@hugin.studio
DTSTAMP:20261106T025252Z
SEQUENCE:46
DTSTART;VALUE=DATE:20261211
DTEND;VALUE=DATE:20261212
SUMMARY:⚑ OpenAI: Custom GPTs retire across ChatGPT plans — GPTs and th
 eir GPT pages become inaccessible
DESCRIPTION:Custom GPTs retire across ChatGPT plans — GPTs and their GPT 
 pages become inaccessible\n\nMOVES TO: Plugins: the FAQ's migration turns 
 a GPT's instructions into a skill within a new plugin and copies its knowl
 edge files. Custom actions\, past conversations\, sharing settings and the
  selected model do not carry over.\n\nBEFORE THIS DATE: If you built a cus
 tom GPT\, migrate it to a plugin and test it before December 11\, and rebu
 ild any custom actions — they do not transfer. If you rely on someone el
 se's GPT\, check for the creator's replacement\; permission to use a GPT d
 oes not give you permission to migrate it.\n\nCaveat: Scheduled\, not exec
 uted. 'The transition affects all ChatGPT plans'\, but Enterprise workspac
 es with an approved deferral retire on February 11\, 2027 instead\, and th
 e FAQ tells every reader to follow the notice for their own account or wor
 kspace. The FAQ is served by a host that refuses this desk's client interm
 ittently.\n\nAuthoritative document (Custom GPT retirement and migration F
 AQ): https://help.openai.com/en/articles/20001519-custom-gpt-retirement-an
 d-migration-faq\nAnnounced in: https://help.openai.com/en/articles/6825453
 -chatgpt-release-notes\n\nTracked by Hugin: https://hugin.studio/deadlines
 ?provider=OpenAI\nOnly dates a provider has published about its own produc
 t appear here.
URL:https://hugin.studio/deadlines?provider=OpenAI
CATEGORIES:OpenAI\,retirement
TRANSP:TRANSPARENT
STATUS:TENTATIVE
BEGIN:VALARM
ACTION:DISPLAY
DESCRIPTION:OpenAI: If you built a custom GPT\, migrate it to a plugin and 
 test it before December 11\, and rebuild any custom actions — they do no
 t transfer. If you rely on someone else's GPT\, check for the creator's re
 placement\; permission to use a GPT does not give you permission to migrat
 e it.
TRIGGER:-P7D
END:VALARM
END:VEVENT
BEGIN:VEVENT
UID:openai-selfserve-finetuning-new-jobs-end@hugin.studio
DTSTAMP:20261106T025252Z
SEQUENCE:554
DTSTART;VALUE=DATE:20270106
DTEND;VALUE=DATE:20270107
SUMMARY:⚑ OpenAI: Active existing customers can no longer create new self
 -serve fine-tuning jobs
DESCRIPTION:Active existing customers can no longer create new self-serve f
 ine-tuning jobs\n\nBEFORE THIS DATE: If a fine-tuned model is part of your
  roadmap\, the job has to exist before this date — creation ends\, not i
 nference.\n\nCaveat: Scoped to CREATING jobs. The ledger states that infer
 ence on already fine-tuned models is disabled only when the underlying bas
 e model is deprecated\, which is a separate date per base model.\n\nAuthor
 itative document (API deprecations ledger): https://developers.openai.com/
 api/docs/deprecations\n\nTracked by Hugin: https://hugin.studio/deadlines?
 provider=OpenAI\nOnly dates a provider has published about its own product
  appear here.
URL:https://hugin.studio/deadlines?provider=OpenAI
CATEGORIES:OpenAI\,definitional
TRANSP:TRANSPARENT
STATUS:TENTATIVE
BEGIN:VALARM
ACTION:DISPLAY
DESCRIPTION:OpenAI: If a fine-tuned model is part of your roadmap\, the job
  has to exist before this date — creation ends\, not inference.
TRIGGER:-P7D
END:VALARM
END:VEVENT
BEGIN:VEVENT
UID:openai-tts-legacy-shutdown@hugin.studio
DTSTAMP:20261106T025252Z
SEQUENCE:554
DTSTART;VALUE=DATE:20270106
DTEND;VALUE=DATE:20270107
SUMMARY:⚑ OpenAI: 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
DESCRIPTION: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\n\nM
 OVES TO: gpt-realtime-2.1-mini\, named for all four ids and in the section
 's own migration sentence.\n\nBEFORE THIS DATE: If you synthesise speech t
 hrough 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 i
 nstruction 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.\n\nCaveat:
  Announced in a ledger section dated October 1\, 2026\, which states the r
 emoval comes 'with at least three months’ notice' — a floor rather tha
 n a figure\, and the shorter of the two notice periods stated by the two s
 ections 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 like
 ly 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 witho
 ut stating the two produce comparable output\, and this desk holds no Open
 AI key and has not compared them.\n\nAuthoritative document (API deprecati
 ons ledger): https://developers.openai.com/api/docs/deprecations\n\nTracke
 d by Hugin: https://hugin.studio/deadlines?provider=OpenAI\nOnly dates a p
 rovider has published about its own product appear here.
URL:https://hugin.studio/deadlines?provider=OpenAI
CATEGORIES:OpenAI\,retirement
TRANSP:TRANSPARENT
STATUS:TENTATIVE
BEGIN:VALARM
ACTION:DISPLAY
DESCRIPTION:OpenAI: If you synthesise speech through tts-1\, tts-1-hd or ei
 ther 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 Rea
 ltime API guide to plan your migration'\, so treat it as a migration to pl
 an rather than a model id to swap.
TRIGGER:-P7D
END:VALARM
END:VEVENT
BEGIN:VEVENT
UID:openai-gpt-4-series-shutdown@hugin.studio
DTSTAMP:20261106T025252Z
SEQUENCE:583
DTSTART;VALUE=DATE:20270114
DTEND;VALUE=DATE:20270115
SUMMARY:⚑ OpenAI: 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\, g
 pt-4.1-2025-04-14 and gpt-4.1-mini-2025-04-14
DESCRIPTION: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-2
 025-04-14 and gpt-4.1-mini-2025-04-14\n\nMOVES TO: gpt-6-luna — the ledg
 er's recommended replacement column names it for every one of the section'
 s four rows.\n\nBEFORE THIS DATE: Search your configuration for those five
  exact snapshot ids and for any fine-tuned model built on them\; the secti
 on states that 'Fine-tuned versions of these models follow the same shutdo
 wn schedule as their underlying base models.' The ledger names gpt-6-luna 
 as the replacement for all of them.\n\nCaveat: Announced in a ledger secti
 on dated October 14\, 2026\, which says developers were 'notified' that da
 y 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 pas
 s on. Every id in this group is a dated snapshot rather than a floating al
 ias\, so code naming one is readable in a diff\; the exposure is instead i
 n fine-tuned models\, which the section sweeps in by reference to their ba
 se models without listing a single one. All four rows name the same replac
 ement\, gpt-6-luna\, for four differently sized models across two families
 \; the ledger names a replacement and does not say it is equivalent to wha
 t it replaces\, and this desk holds no OpenAI key and has not compared the
 m. The ledger records a schedule and keeps carrying ids after their dates\
 , so it cannot by itself confirm a shutdown happened.\n\nAuthoritative doc
 ument (API deprecations ledger): https://developers.openai.com/api/docs/de
 precations\n\nTracked by Hugin: https://hugin.studio/deadlines?provider=Op
 enAI\nOnly dates a provider has published about its own product appear her
 e.
URL:https://hugin.studio/deadlines?provider=OpenAI
CATEGORIES:OpenAI\,retirement
TRANSP:TRANSPARENT
STATUS:TENTATIVE
BEGIN:VALARM
ACTION:DISPLAY
DESCRIPTION:OpenAI: 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 replacem
 ent for all of them.
TRIGGER:-P7D
END:VALARM
END:VEVENT
BEGIN:VEVENT
UID:openai-legacy-audio-realtime-shutdown@hugin.studio
DTSTAMP:20261106T025252Z
SEQUENCE:610
DTSTART;VALUE=DATE:20270120
DTEND;VALUE=DATE:20270121
SUMMARY:⚑ OpenAI: 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
DESCRIPTION:Every legacy audio\, realtime and transcription family is remov
 ed from the API — gpt-realtime\, gpt-audio\, gpt-4o-audio\, gpt-4o-realt
 ime\, their mini variants\, and gpt-4o-mini-transcribe\n\nMOVES TO: gpt-re
 altime-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.\n\nB
 EFORE THIS DATE: Repoint at the named replacements: gpt-realtime-2.1 and g
 pt-realtime-2.1-mini for realtime\, gpt-audio-1.5 for every audio family\,
  gpt-4o-mini-transcribe-2025-12-15 for transcription.\n\nCaveat: 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 d
 ate with nothing in your code naming a version that could warn you\, the c
 hatgpt-image-latest trap at family scale.\n\nAuthoritative document (API d
 eprecations ledger): https://developers.openai.com/api/docs/deprecations\n
 \nTracked by Hugin: https://hugin.studio/deadlines?provider=OpenAI\nOnly d
 ates a provider has published about its own product appear here.
URL:https://hugin.studio/deadlines?provider=OpenAI
CATEGORIES:OpenAI\,retirement
TRANSP:TRANSPARENT
STATUS:TENTATIVE
BEGIN:VALARM
ACTION:DISPLAY
DESCRIPTION:OpenAI: 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.
TRIGGER:-P7D
END:VALARM
END:VEVENT
BEGIN:VEVENT
UID:openai-transcription-legacy-shutdown@hugin.studio
DTSTAMP:20261106T025252Z
SEQUENCE:488
DTSTART;VALUE=DATE:20270226
DTEND;VALUE=DATE:20270227
SUMMARY:⚑ OpenAI: The legacy transcription models are removed from the AP
 I — whisper-1\, gpt-4o-transcribe\, gpt-4o-mini-transcribe and gpt-4o-tr
 anscribe-diarize
DESCRIPTION:The legacy transcription models are removed from the API — wh
 isper-1\, gpt-4o-transcribe\, gpt-4o-mini-transcribe and gpt-4o-transcribe
 -diarize\n\nMOVES TO: gpt-live-transcribe or gpt-transcribe\, named for al
 l four ids.\n\nBEFORE THIS DATE: Repoint at gpt-live-transcribe or gpt-tra
 nscribe\, the two replacements the ledger names for all four ids.\n\nCavea
 t: Announced August 26\, 2026\, and the farthest date on the ledger — wh
 ich 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.\n\nAuthoritativ
 e document (API deprecations ledger): https://developers.openai.com/api/do
 cs/deprecations\n\nTracked by Hugin: https://hugin.studio/deadlines?provid
 er=OpenAI\nOnly dates a provider has published about its own product appea
 r here.
URL:https://hugin.studio/deadlines?provider=OpenAI
CATEGORIES:OpenAI\,retirement
TRANSP:TRANSPARENT
STATUS:TENTATIVE
BEGIN:VALARM
ACTION:DISPLAY
DESCRIPTION:OpenAI: Repoint at gpt-live-transcribe or gpt-transcribe\, the 
 two replacements the ledger names for all four ids.
TRIGGER:-P7D
END:VALARM
END:VEVENT
BEGIN:VEVENT
UID:openai-gpt-5-1-codex-nano-shutdown@hugin.studio
DTSTAMP:20261106T025252Z
SEQUENCE:165
DTSTART;VALUE=DATE:20270401
DTEND;VALUE=DATE:20270402
SUMMARY:⚑ OpenAI: Three models are removed from the API — gpt-5.1\, gpt
 -5.3-codex and gpt-5.4-nano
DESCRIPTION:Three models are removed from the API — gpt-5.1\, gpt-5.3-cod
 ex and gpt-5.4-nano\n\nMOVES TO: gpt-6-sol for both gpt-5.1 and gpt-5.3-co
 dex\, and gpt-6-luna for gpt-5.4-nano — the ledger's recommended replace
 ment column for all three rows.\n\nBEFORE THIS DATE: Search your configura
 tion 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 shut
 down date': gpt-6-sol for the first two\, gpt-6-luna for gpt-5.4-nano.\n\n
 Caveat: Announced in a ledger section dated October 1\, 2026\, which state
 s the removal comes 'with six months’ notice'. gpt-5.1 is a floating maj
 or id rather than a dated snapshot\, so code naming it keeps working to th
 e 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 repla
 cement\, 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. Th
 e ledger records a schedule and keeps carrying ids after their dates\, so 
 it cannot by itself confirm a shutdown happened.\n\nAuthoritative document
  (API deprecations ledger): https://developers.openai.com/api/docs/depreca
 tions\n\nTracked by Hugin: https://hugin.studio/deadlines?provider=OpenAI\
 nOnly dates a provider has published about its own product appear here.
URL:https://hugin.studio/deadlines?provider=OpenAI
CATEGORIES:OpenAI\,retirement
TRANSP:TRANSPARENT
STATUS:TENTATIVE
BEGIN:VALARM
ACTION:DISPLAY
DESCRIPTION:OpenAI: Search your configuration for the exact ids gpt-5.1\, g
 pt-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 firs
 t two\, gpt-6-luna for gpt-5.4-nano.
TRIGGER:-P7D
END:VALARM
END:VEVENT
BEGIN:VEVENT
UID:openai-evals-read-only@hugin.studio
DTSTAMP:20261106T025252Z
SEQUENCE:364
DTSTART;VALUE=DATE:20261031
DTEND;VALUE=DATE:20261101
SUMMARY:⚑ OpenAI: Existing evals on the deprecated Evals platform become 
 read-only
DESCRIPTION:Existing evals on the deprecated Evals platform become read-onl
 y\n\nBEFORE THIS DATE: Export or migrate any eval you still need to edit b
 efore this date — after it\, existing evals can be read but not changed\
 , a month before the platform shuts down.\n\nCaveat: The first of two date
 d steps for the Evals platform — the shutdown itself is a separate row o
 n November 30. Announced June 3\, 2026\; the ledger names Promptfoo as a m
 igration path.\n\nAuthoritative document (API deprecations ledger): https:
 //developers.openai.com/api/docs/deprecations\n\nTracked by Hugin: https:/
 /hugin.studio/deadlines?provider=OpenAI\nOnly dates a provider has publish
 ed about its own product appear here.
URL:https://hugin.studio/deadlines?provider=OpenAI
CATEGORIES:OpenAI\,definitional
TRANSP:TRANSPARENT
STATUS:CONFIRMED
END:VEVENT
BEGIN:VEVENT
UID:openai-custom-gpts-enterprise-creation-cutoff@hugin.studio
DTSTAMP:20261106T025252Z
SEQUENCE:338
DTSTART;VALUE=DATE:20261026
DTEND;VALUE=DATE:20261027
SUMMARY:⚑ OpenAI: Affected ChatGPT Enterprise workspaces can no longer cr
 eate new custom GPTs
DESCRIPTION:Affected ChatGPT Enterprise workspaces can no longer create new
  custom GPTs\n\nBEFORE THIS DATE: Enterprise workspaces: publish any draft
  GPT you intend to migrate before this date — migration uses a GPT's lat
 est published version\, and drafts and unpublished edits do not transfer.\
 n\nCaveat: Planned\, and the FAQ says the Enterprise dates 'are subject to
  change'. The Internet Archive's September 18 copy of the same FAQ gave Se
 ptember 25 for this cutoff\; no release note records the change. Edits to 
 existing\, unmigrated GPTs are stated to continue after the cutoff.\n\nAut
 horitative document (Custom GPT retirement and migration FAQ): https://hel
 p.openai.com/en/articles/20001519-custom-gpt-retirement-and-migration-faq\
 n\nTracked by Hugin: https://hugin.studio/deadlines?provider=OpenAI\nOnly 
 dates a provider has published about its own product appear here.
URL:https://hugin.studio/deadlines?provider=OpenAI
CATEGORIES:OpenAI\,definitional
TRANSP:TRANSPARENT
STATUS:CONFIRMED
END:VEVENT
BEGIN:VEVENT
UID:openai-legacy-snapshots-october-shutdown@hugin.studio
DTSTAMP:20261106T025252Z
SEQUENCE:335
DTSTART;VALUE=DATE:20261023
DTEND;VALUE=DATE:20261024
SUMMARY:⚑ OpenAI: A second legacy wave shuts down seventeen listed ids: t
 he gpt-3.5/GPT-4-era snapshots (gpt-3.5-turbo-0125\, gpt-4-0613\, gpt-4-11
 06-preview\, gpt-4-turbo\, gpt-4.1-nano\, gpt-4o-2024-05-13)\, the reasoni
 ng 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-davin
 ci-002
DESCRIPTION: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-previ
 ew\, gpt-4-turbo\, gpt-4.1-nano\, gpt-4o-2024-05-13)\, the reasoning model
 s 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\n
 \nMOVES 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.\n\nBEFORE THIS DATE: Substitutes are named per i
 d — gpt-5.6-terra for the 3.5 and o4-mini lines\, gpt-5.6-sol for the GP
 T-4 and o1/o3 lines\, gpt-5.6-luna for the nano line\, gpt-image-2 for gpt
 -image-1. Check which of your pins is in which wave\; the September and Oc
 tober groups do not share a date.\n\nCaveat: A separate group from the Sep
 tember wave\, announced on its own date. The ledger lists each snapshot al
 ias alongside the model name\, so a pin on either form is covered. Until A
 ugust 26 this row described only six of the seventeen ids\; the fuller lis
 t above is what the cited section has carried since at least August 10.\n\
 nAuthoritative document (API deprecations ledger): https://developers.open
 ai.com/api/docs/deprecations\n\nTracked by Hugin: https://hugin.studio/dea
 dlines?provider=OpenAI\nOnly dates a provider has published about its own 
 product appear here.
URL:https://hugin.studio/deadlines?provider=OpenAI
CATEGORIES:OpenAI\,retirement
TRANSP:TRANSPARENT
STATUS:CONFIRMED
END:VEVENT
BEGIN:VEVENT
UID:openai-gpt-rosalind-billing-starts@hugin.studio
DTSTAMP:20261106T025252Z
SEQUENCE:275
DTSTART;VALUE=DATE:20261005
DTEND;VALUE=DATE:20261006
SUMMARY:⚑ OpenAI: Billing begins for GPT-Rosalind (gpt-rosalind-research)
 \, the trusted-access life-sciences model
DESCRIPTION:Billing begins for GPT-Rosalind (gpt-rosalind-research)\, the t
 rusted-access life-sciences model\n\nBEFORE THIS DATE: Approved trusted-ac
 cess organisations using gpt-rosalind-research: usage is billed from Octob
 er 5 at $5 per 1M input tokens\, $0.50 cached input and $25 output — set
  a budget or usage limit before the date.\n\nCaveat: Only approved organis
 ations in the trusted-access program can use the model\, so almost no read
 er 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 billin
 g begins then.\n\nAuthoritative document (OpenAI API changelog): https://d
 evelopers.openai.com/api/docs/changelog\n\nTracked by Hugin: https://hugin
 .studio/deadlines?provider=OpenAI\nOnly dates a provider has published abo
 ut its own product appear here.
URL:https://hugin.studio/deadlines?provider=OpenAI
CATEGORIES:OpenAI\,price-change
TRANSP:TRANSPARENT
STATUS:CONFIRMED
END:VEVENT
BEGIN:VEVENT
UID:openai-gpt-5-4-cyber-shutdown@hugin.studio
DTSTAMP:20261106T025252Z
SEQUENCE:271
DTSTART;VALUE=DATE:20261001
DTEND;VALUE=DATE:20261002
SUMMARY:⚑ OpenAI: gpt-5.4-cyber is removed from the API
DESCRIPTION:gpt-5.4-cyber is removed from the API\n\nMOVES TO: 'The most ca
 pable cyber model available to you.' — the ledger's replacement column s
 ince September 30. Until then it named gpt-5.6-cyber\, which OpenAI's mode
 l catalog still lists.\n\nBEFORE THIS DATE: Repoint any pinned gpt-5.4-cyb
 er model id before October 1 at a cyber model your organisation can actual
 ly call. The ledger no longer names gpt-5.6-cyber\; OpenAI's changelog say
 s GPT-5.6 Cyber comes through Daybreak Red\, whose models 'require separat
 e approval and provisioning'\, so confirm your access before relying on it
 .\n\nCaveat: Announced in a ledger section dated September 11\, 2026 — t
 wenty 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 changelo
 g entry\; the date stayed October 1. The ledger records a schedule\; it ke
 eps carrying ids after their date\, so it cannot by itself confirm a shutd
 own happened.\n\nAuthoritative document (API deprecations ledger): https:/
 /developers.openai.com/api/docs/deprecations\n\nTracked by Hugin: https://
 hugin.studio/deadlines?provider=OpenAI\nOnly dates a provider has publishe
 d about its own product appear here.
URL:https://hugin.studio/deadlines?provider=OpenAI
CATEGORIES:OpenAI\,retirement
TRANSP:TRANSPARENT
STATUS:CONFIRMED
END:VEVENT
BEGIN:VEVENT
UID:openai-legacy-snapshots-september-shutdown@hugin.studio
DTSTAMP:20261106T025252Z
SEQUENCE:3156
DTSTART;VALUE=DATE:20260928
DTEND;VALUE=DATE:20260929
SUMMARY:⚑ OpenAI: Legacy snapshots gpt-3.5-turbo-instruct\, babbage-002\,
  davinci-002 and gpt-3.5-turbo-1106 shut down
DESCRIPTION:Legacy snapshots gpt-3.5-turbo-instruct\, babbage-002\, davinci
 -002 and gpt-3.5-turbo-1106 shut down\n\nMOVES TO: gpt-5.6-terra\, named f
 or all four ids.\n\nBEFORE THIS DATE: Move any pinned legacy snapshot to t
 he named substitute\, gpt-5.6-terra\, before the date.\n\nWHAT HAPPENED (f
 iled 2026-10-02 — Not establishable by this desk):\nFiled as past by Ope
 nAI'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 da
 te 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.\n\nCaveat: 
 Part of a stated multi-wave retirement of older models with declining usag
 e. A substitute model is named for every id in this group.\n\nAuthoritativ
 e document (API deprecations ledger): https://developers.openai.com/api/do
 cs/deprecations\n\nTracked by Hugin: https://hugin.studio/deadlines?provid
 er=OpenAI\nOnly dates a provider has published about its own product appea
 r here.
URL:https://hugin.studio/deadlines?provider=OpenAI
CATEGORIES:OpenAI\,retirement
TRANSP:TRANSPARENT
STATUS:CONFIRMED
END:VEVENT
BEGIN:VEVENT
UID:openai-videos-api-sora2-shutdown@hugin.studio
DTSTAMP:20261106T025252Z
SEQUENCE:3152
DTSTART;VALUE=DATE:20260924
DTEND;VALUE=DATE:20260925
SUMMARY:⚑ OpenAI: The Videos API and the entire Sora 2 model family shut 
 down
DESCRIPTION:The Videos API and the entire Sora 2 model family shut down\n\n
 NOTHING TO MOVE TO: The ledger's replacement column reads "---" for all si
 x rows\, and no migration sentence appears anywhere in the announcement. M
 easured 2026-09-07: these are the only six rows on the page in that condit
 ion\, out of 49 with a replacement column.\n\nBEFORE THIS DATE: Decide wha
 t replaces it\, not which model to switch to. This is a vendor evaluation 
 with a date on it — new contract\, new prices\, a different safety postu
 re — so it needs whoever can authorise that\, not only whoever owns the 
 code.\n\nWHAT HAPPENED (filed 2026-09-27 — Confirmed by this desk's own 
 re-read):\nShut down\, by OpenAI's own account and by wire. The sora-2 mod
 el page now reads 'The Sora 2 models and Videos API were shut down on Sept
 ember 24\, 2026 and are no longer available. There is no one-to-one replac
 ement 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 al
 l six rows under 'Upcoming deprecations' three days after the date\, and t
 he help centre still says the API 'will be discontinued'.\n\nCaveat: Cover
 s the Videos API plus sora-2\, sora-2-pro and three dated snapshots. The c
 onsumer app went earlier\, on April 26\, 2026\; the help-centre article fo
 r it commits to deleting Sora content after a final export window it descr
 ibes only conditionally.\n\nAuthoritative document (API deprecations ledge
 r): https://developers.openai.com/api/docs/deprecations\n\nTracked by Hugi
 n: https://hugin.studio/deadlines?provider=OpenAI\nOnly dates a provider h
 as published about its own product appear here.
URL:https://hugin.studio/deadlines?provider=OpenAI
CATEGORIES:OpenAI\,retirement
TRANSP:TRANSPARENT
STATUS:CONFIRMED
END:VEVENT
BEGIN:VEVENT
UID:openai-gpt54-codex-signin-retirement@hugin.studio
DTSTAMP:20261106T025252Z
SEQUENCE:3308
DTSTART;VALUE=DATE:20260831
DTEND;VALUE=DATE:20260901
SUMMARY:⚑ OpenAI: GPT-5.4 and GPT-5.4 mini stop being available in Codex 
 for users signed in with ChatGPT
DESCRIPTION:GPT-5.4 and GPT-5.4 mini stop being available in Codex for user
 s signed in with ChatGPT\n\nMOVES TO: A recommended replacement model in C
 odex\, or the same models via API-key authentication — the retirement is
  scoped to an access path\, not to the model.\n\nBEFORE THIS DATE: If you 
 use those models in Codex via ChatGPT sign-in\, switch to a recommended re
 placement or authenticate with an API key.\n\nWHAT HAPPENED (filed 2026-09
 -14 — Confirmed by this desk's own re-read):\nThe page still describes i
 t as upcoming. Read 2026-09-14: the Codex models page\, since reworded\, s
 ays 'GPT-5.4 and GPT-5.4 mini retire from Codex on August 31\, 2026' and s
 till offers the codex -m gpt-5.4 and codex -m gpt-5.4-mini commands. The p
 age was not updated\; whether ChatGPT sign-in access actually ended is not
  something it settles.\n\nCaveat: Scoped to an access path\, not the model
 s: both remain on the OpenAI API and in Codex sessions authenticated with 
 an API key.\n\nAuthoritative document (Codex models doc): https://learn.ch
 atgpt.com/codex/models\nAnnounced in: https://learn.chatgpt.com/docs/chang
 elog\n\nTracked by Hugin: https://hugin.studio/deadlines?provider=OpenAI\n
 Only dates a provider has published about its own product appear here.
URL:https://hugin.studio/deadlines?provider=OpenAI
CATEGORIES:OpenAI\,retirement
TRANSP:TRANSPARENT
STATUS:CONFIRMED
END:VEVENT
BEGIN:VEVENT
UID:openai-dalle-gpt-retirement@hugin.studio
DTSTAMP:20261106T025252Z
SEQUENCE:3307
DTSTART;VALUE=DATE:20260830
DTEND;VALUE=DATE:20260831
SUMMARY:⚑ OpenAI: The official DALL·E GPT is retired in ChatGPT
DESCRIPTION:The official DALL·E GPT is retired in ChatGPT\n\nMOVES TO: Ima
 ge generation in ChatGPT itself\; the notice states user-created GPTs with
  image generation enabled are unaffected.\n\nBEFORE THIS DATE: Download an
 y images you want to keep before this date — the notice says so explicit
 ly.\n\nWHAT HAPPENED (filed 2026-09-14 — Not establishable by this desk)
 :\nNot establishable. The ChatGPT release notes\, readable on 2026-09-14 a
 fter refusing this desk's client through September 1\, still carry only th
 e notice 'On August 30\, 2026\, we're retiring the official DALL·E GPT in
  ChatGPT'\; nothing after it records the retirement.\n\nCaveat: User-creat
 ed GPTs with image generation enabled are stated to be unaffected. ChatGPT
  Images remains available for creating and editing.\n\nAuthoritative docum
 ent (ChatGPT release notes): https://help.openai.com/en/articles/6825453-c
 hatgpt-release-notes\n\nTracked by Hugin: https://hugin.studio/deadlines?p
 rovider=OpenAI\nOnly dates a provider has published about its own product 
 appear here.
URL:https://hugin.studio/deadlines?provider=OpenAI
CATEGORIES:OpenAI\,retirement
TRANSP:TRANSPARENT
STATUS:CONFIRMED
END:VEVENT
BEGIN:VEVENT
UID:openai-assistants-api-shutdown@hugin.studio
DTSTAMP:20261106T025252Z
SEQUENCE:3282
DTSTART;VALUE=DATE:20260826
DTEND;VALUE=DATE:20260827
SUMMARY:⚑ OpenAI: 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 Microsof
 t Foundry Agents instead
DESCRIPTION: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\n\nMOVES 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.\n\nBEFORE THIS DATE: Migra
 te before the date\, but check which vendor you are actually on first: dir
 ect OpenAI integrations go to the Responses or Conversations API\, Azure O
 penAI deployments go to Microsoft Foundry Agents. The two notices name dif
 ferent destinations and neither mentions the other.\n\nWHAT HAPPENED (file
 d 2026-08-27 — Confirmed by this desk's own re-read):\nShut down\, and e
 stablishable from outside: unauthenticated\, /v1/assistants returns 404 wi
 th 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 s
 paced probes across 2026-08-26 and 2026-08-27\, each run with the missing-
 route control alongside\, never moved. Microsoft's Foundry (classic) notic
 e\, future-tense on the morning of the 26th\, now reads "The Assistants AP
 I is retired."\n\nCaveat: 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 carr
 ied only the OpenAI exit\, which was accurate for OpenAI's surface and sil
 ent 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\n\nAuthoritative document (API deprecations ledger): http
 s://developers.openai.com/api/docs/deprecations\n\nTracked by Hugin: https
 ://hugin.studio/deadlines?provider=OpenAI\nOnly dates a provider has publi
 shed about its own product appear here.
URL:https://hugin.studio/deadlines?provider=OpenAI
CATEGORIES:OpenAI\,retirement
TRANSP:TRANSPARENT
STATUS:CONFIRMED
END:VEVENT
BEGIN:VEVENT
UID:openai-o3-chatgpt-retirement@hugin.studio
DTSTAMP:20261106T025252Z
SEQUENCE:3282
DTSTART;VALUE=DATE:20260826
DTEND;VALUE=DATE:20260827
SUMMARY:OpenAI: OpenAI o3 is retired from ChatGPT after a stated 90-day sun
 set
DESCRIPTION:OpenAI o3 is retired from ChatGPT after a stated 90-day sunset\
 n\nMOVES TO: GPT-5.6 in ChatGPT — the release notes retire o3 into the c
 urrent default rather than naming a per-model substitute.\n\nWHAT HAPPENED
  (filed 2026-09-14 — Not establishable by this desk):\nNot 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'\, i
 n the future tense\, and no later entry records the retirement. A schedule
  nobody updated cannot show whether it was kept.\n\nCaveat: A retirement n
 otice records that access is ending. It says nothing about the model's qua
 lity or about why.\n\nAuthoritative document (Model release notes): https:
 //help.openai.com/en/articles/9624314-model-release-notes\n\nTracked by Hu
 gin: https://hugin.studio/deadlines?provider=OpenAI\nOnly dates a provider
  has published about its own product appear here.
URL:https://hugin.studio/deadlines?provider=OpenAI
CATEGORIES:OpenAI\,retirement
TRANSP:TRANSPARENT
STATUS:CONFIRMED
END:VEVENT
BEGIN:VEVENT
UID:openai-chat-latest-api-shutdown@hugin.studio
DTSTAMP:20261106T025252Z
SEQUENCE:3245
DTSTART;VALUE=DATE:20260810
DTEND;VALUE=DATE:20260811
SUMMARY:⚑ OpenAI: gpt-5.2-chat-latest and gpt-5.3-chat-latest shut down o
 n the API\, replaced by gpt-5.6-sol
DESCRIPTION:gpt-5.2-chat-latest and gpt-5.3-chat-latest shut down on the AP
 I\, replaced by gpt-5.6-sol\n\nMOVES TO: gpt-5.6-sol\, named in the ledger
 's replacement column for both aliases.\n\nBEFORE THIS DATE: If your code 
 pins either alias\, move it to a supported model before the date.\n\nWHAT 
 HAPPENED (filed 2026-08-10 — Confirmed by this desk's own re-read):\nExe
 cuted on schedule\, 94 days after the May 8 notice. The ledger still carri
 es 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
 .\n\nCaveat: Scoped to the two dated chat-latest aliases. The deprecations
  ledger is the provider's own schedule and is where any change to this dat
 e would appear.\n\nAuthoritative document (API deprecations ledger): https
 ://developers.openai.com/api/docs/deprecations\n\nTracked by Hugin: https:
 //hugin.studio/deadlines?provider=OpenAI\nOnly dates a provider has publis
 hed about its own product appear here.
URL:https://hugin.studio/deadlines?provider=OpenAI
CATEGORIES:OpenAI\,retirement
TRANSP:TRANSPARENT
STATUS:CONFIRMED
END:VEVENT
BEGIN:VEVENT
UID:openai-atlas-shutdown@hugin.studio
DTSTAMP:20261106T025252Z
SEQUENCE:3223
DTSTART;VALUE=DATE:20260809
DTEND;VALUE=DATE:20260810
SUMMARY:OpenAI: The Atlas browser stops working
DESCRIPTION:The Atlas browser stops working\n\nMOVES TO: ChatGPT for browse
 r-based agentic work\, named in the article's own title.\n\nWHAT HAPPENED 
 (filed 2026-08-10 — Not establishable by this desk):\nReported to have h
 appened\, but not establishable from any OpenAI page this desk can read: h
 elp.openai.com\, openai.com and chatgpt.com all refuse or challenge the id
 entifying client\, while the developer docs serve it the whole document.\n
 \nCaveat: 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
 .\n\nAuthoritative document (Atlas retirement article): https://help.opena
 i.com/en/articles/20001371-evolving-atlas-into-chatgpt-for-browser-based-a
 gentic-work\nAnnounced in: https://help.openai.com/en/articles/6825453-cha
 tgpt-release-notes\n\nTracked by Hugin: https://hugin.studio/deadlines?pro
 vider=OpenAI\nOnly dates a provider has published about its own product ap
 pear here.
URL:https://hugin.studio/deadlines?provider=OpenAI
CATEGORIES:OpenAI\,retirement
TRANSP:TRANSPARENT
STATUS:CONFIRMED
END:VEVENT
END:VCALENDAR