BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//Hugin//Provider deadline board//EN
CALSCALE:GREGORIAN
METHOD:PUBLISH
X-WR-CALNAME:Hugin — provider deadlines
X-WR-CALDESC:Every end date a provider has published about its own product 
 and this desk is tracking: promotional windows closing\, prices changing\,
  models and APIs retiring. Only published dates\; nothing inferred.
X-PUBLISHED-TTL:PT12H
REFRESH-INTERVAL;VALUE=DURATION:PT12H
BEGIN:VEVENT
UID:openai-videos-api-sora2-shutdown@hugin.studio
DTSTAMP:20260921T112823Z
SEQUENCE:3152
DTSTART;VALUE=DATE:20260924
DTEND;VALUE=DATE:20260925
SUMMARY:⚑ NO SUCCESSOR — OpenAI: The Videos API and the entire Sora 2 m
 odel 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\nCaveat: 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.\n\nAuthoritative document (
 API deprecations ledger): https://developers.openai.com/api/docs/deprecati
 ons\n\nTracked by Hugin: https://hugin.studio/deadlines\nOnly dates a prov
 ider has published about its own product appear here.
URL:https://hugin.studio/deadlines
CATEGORIES:OpenAI\,retirement
TRANSP:TRANSPARENT
STATUS:TENTATIVE
BEGIN:VALARM
ACTION:DISPLAY
DESCRIPTION:OpenAI: Decide what replaces it\, not which model to switch to.
  This is a vendor evaluation with a date on it — new contract\, new pric
 es\, a different safety posture — so it needs whoever can authorise that
 \, not only whoever owns the code.
TRIGGER:-P7D
END:VALARM
BEGIN:VALARM
ACTION:DISPLAY
DESCRIPTION:OpenAI: no successor is published for this. Deciding what repla
 ces it is a vendor question\, not a code change — start now.
TRIGGER:-P30D
END:VALARM
END:VEVENT
BEGIN:VEVENT
UID:openai-legacy-snapshots-september-shutdown@hugin.studio
DTSTAMP:20260921T112823Z
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\nCaveat: Part of 
 a stated multi-wave retirement of older models with declining usage. A sub
 stitute model is named for every id in this group.\n\nAuthoritative docume
 nt (API deprecations ledger): https://developers.openai.com/api/docs/depre
 cations\n\nTracked by Hugin: https://hugin.studio/deadlines\nOnly dates a 
 provider has published about its own product appear here.
URL:https://hugin.studio/deadlines
CATEGORIES:OpenAI\,retirement
TRANSP:TRANSPARENT
STATUS:TENTATIVE
BEGIN:VALARM
ACTION:DISPLAY
DESCRIPTION:OpenAI: Move any pinned legacy snapshot to the named substitute
 \, gpt-5.6-terra\, before the date.
TRIGGER:-P7D
END:VALARM
END:VEVENT
BEGIN:VEVENT
UID:google-gemini-omni-flash-preview-deprecation@hugin.studio
DTSTAMP:20260921T112823Z
SEQUENCE:3179
DTSTART;VALUE=DATE:20260930
DTEND;VALUE=DATE:20261001
SUMMARY:⚑ Google: The gemini-omni-flash-preview endpoint is deprecated in
  the Gemini API
DESCRIPTION:The gemini-omni-flash-preview endpoint is deprecated in the Gem
 ini API\n\nMOVES TO: gemini-omni-1.1-flash\, released August 27\, 2026 as 
 the GA version of the same model.\n\nBEFORE THIS DATE: Search your configu
 ration for the exact string gemini-omni-flash-preview and repoint it at ge
 mini-omni-1.1-flash.\n\nCaveat: Google's sentence says the endpoint 'will 
 be deprecated'\, not removed\, and names the GA model in the neighbouring 
 entry rather than as a stated replacement. The changelog redirects an unau
 thenticated plain client to a sign-in page\, so this desk reads it through
  a rendering fetcher.\n\nAuthoritative document (Gemini API changelog): ht
 tps://ai.google.dev/gemini-api/docs/changelog\n\nTracked by Hugin: https:/
 /hugin.studio/deadlines\nOnly dates a provider has published about its own
  product appear here.
URL:https://hugin.studio/deadlines
CATEGORIES:Google\,retirement
TRANSP:TRANSPARENT
STATUS:TENTATIVE
BEGIN:VALARM
ACTION:DISPLAY
DESCRIPTION:Google: Search your configuration for the exact string gemini-o
 mni-flash-preview and repoint it at gemini-omni-1.1-flash.
TRIGGER:-P7D
END:VALARM
END:VEVENT
BEGIN:VEVENT
UID:openai-gpt-5-4-cyber-shutdown@hugin.studio
DTSTAMP:20260921T112823Z
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: gpt-5.6-cybe
 r\, named in both the announcement sentence and the ledger's replacement c
 olumn.\n\nBEFORE THIS DATE: Repoint any pinned gpt-5.4-cyber model id at g
 pt-5.6-cyber before the date.\n\nCaveat: Announced in a ledger section dat
 ed September 11\, 2026 — twenty days of notice\, the shortest on the led
 ger's pending schedule. The ledger records a schedule\; it keeps carrying 
 ids after their date\, so it cannot by itself confirm a shutdown happened.
 \n\nAuthoritative document (API deprecations ledger): https://developers.o
 penai.com/api/docs/deprecations\n\nTracked by Hugin: https://hugin.studio/
 deadlines\nOnly dates a provider has published about its own product appea
 r here.
URL:https://hugin.studio/deadlines
CATEGORIES:OpenAI\,retirement
TRANSP:TRANSPARENT
STATUS:TENTATIVE
BEGIN:VALARM
ACTION:DISPLAY
DESCRIPTION:OpenAI: Repoint any pinned gpt-5.4-cyber model id at gpt-5.6-cy
 ber before the date.
TRIGGER:-P7D
END:VALARM
END:VEVENT
BEGIN:VEVENT
UID:github-copilot-four-model-deprecation@hugin.studio
DTSTAMP:20260921T112823Z
SEQUENCE:272
DTSTART;VALUE=DATE:20261002
DTEND;VALUE=DATE:20261003
SUMMARY:⚑ GitHub: GitHub Copilot deprecates Claude Opus 4.7\, Gemini 3.5 
 Flash\, Gemini 3.6 Flash and Kimi K2.7 Code across all Copilot experiences
DESCRIPTION:GitHub Copilot deprecates Claude Opus 4.7\, Gemini 3.5 Flash\, 
 Gemini 3.6 Flash and Kimi K2.7 Code across all Copilot experiences\n\nMOVE
 S TO: Claude Opus 5 for Opus 4.7\, Gemini 3.8 Flash for both Gemini Flash 
 models\, Kimi K3 for Kimi K2.7 Code — GitHub's suggested alternatives.\n
 \nBEFORE THIS DATE: Copilot Business and Enterprise administrators: enable
  the alternative models in Copilot model policies before the date — GitH
 ub's notice says they may need to\, and until they do users lose the old m
 odel without getting the new one.\n\nCaveat: A retirement from ONE tool\, 
 not from the model's maker: Anthropic's deprecations page lists claude-opu
 s-4-7 as Active with a retirement not sooner than April 16\, 2027\, and Go
 ogle lists no date for its Gemini 3.x Flash models. The models remain avai
 lable elsewhere\; they leave Copilot.\n\nAuthoritative document (GitHub ch
 angelog notice): https://github.blog/changelog/2026-09-03-upcoming-depreca
 tion-of-selected-github-copilot-models\n\nTracked by Hugin: https://hugin.
 studio/deadlines\nOnly dates a provider has published about its own produc
 t appear here.
URL:https://hugin.studio/deadlines
CATEGORIES:GitHub\,retirement
TRANSP:TRANSPARENT
STATUS:TENTATIVE
BEGIN:VALARM
ACTION:DISPLAY
DESCRIPTION:GitHub: Copilot Business and Enterprise administrators: enable 
 the alternative models in Copilot model policies before the date — GitHu
 b's notice says they may need to\, and until they do users lose the old mo
 del without getting the new one.
TRIGGER:-P7D
END:VALARM
END:VEVENT
BEGIN:VEVENT
UID:google-gemini-2-5-flash-image-shutdown@hugin.studio
DTSTAMP:20260921T112823Z
SEQUENCE:272
DTSTART;VALUE=DATE:20261002
DTEND;VALUE=DATE:20261003
SUMMARY:⚑ Google: gemini-2.5-flash-image reaches its earliest listed shut
 down date in the Gemini API
DESCRIPTION:gemini-2.5-flash-image reaches its earliest listed shutdown dat
 e in the Gemini API\n\nMOVES TO: gemini-3.1-flash-image-preview\, named in
  the deprecations table's replacement column.\n\nBEFORE THIS DATE: Move ca
 lls to gemini-3.1-flash-image-preview before the date. Google lists Octobe
 r 2 as the earliest possible shutdown\, so the model may keep answering pa
 st it — plan for the date\, do not wait for a failure.\n\nCaveat: Google
 's table states listed shutdown dates are 'the earliest possible dates on 
 which a model might be retired' — a floor\, not a schedule. The page red
 irects an unauthenticated plain client to a sign-in flow\, so this desk re
 ads it through a rendering fetcher.\n\nAuthoritative document (Gemini API 
 deprecations): https://ai.google.dev/gemini-api/docs/deprecations\n\nTrack
 ed by Hugin: https://hugin.studio/deadlines\nOnly dates a provider has pub
 lished about its own product appear here.
URL:https://hugin.studio/deadlines
CATEGORIES:Google\,retirement
TRANSP:TRANSPARENT
STATUS:TENTATIVE
BEGIN:VALARM
ACTION:DISPLAY
DESCRIPTION:Google: Move calls to gemini-3.1-flash-image-preview before the
  date. Google lists October 2 as the earliest possible shutdown\, so the m
 odel may keep answering past it — plan for the date\, do not wait for a 
 failure.
TRIGGER:-P7D
END:VALARM
END:VEVENT
BEGIN:VEVENT
UID:openai-legacy-snapshots-october-shutdown@hugin.studio
DTSTAMP:20260921T112823Z
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\nOnly dates a provider has published about its own product appear h
 ere.
URL:https://hugin.studio/deadlines
CATEGORIES:OpenAI\,retirement
TRANSP:TRANSPARENT
STATUS:TENTATIVE
BEGIN:VALARM
ACTION:DISPLAY
DESCRIPTION:OpenAI: Substitutes are named 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 the nano line\, gpt-image-2 for gpt-image-1. Check which of you
 r pins is in which wave\; the September and October groups do not share a 
 date.
TRIGGER:-P7D
END:VALARM
END:VEVENT
BEGIN:VEVENT
UID:openai-evals-read-only@hugin.studio
DTSTAMP:20260921T112823Z
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\nOnly dates a provider has published about its own
  product appear here.
URL:https://hugin.studio/deadlines
CATEGORIES:OpenAI\,definitional
TRANSP:TRANSPARENT
STATUS:TENTATIVE
BEGIN:VALARM
ACTION:DISPLAY
DESCRIPTION:OpenAI: Export or migrate any eval you still need to edit befor
 e this date — after it\, existing evals can be read but not changed\, a 
 month before the platform shuts down.
TRIGGER:-P7D
END:VALARM
END:VEVENT
BEGIN:VEVENT
UID:xai-grok-imagine-image-quality-retirement@hugin.studio
DTSTAMP:20260921T112823Z
SEQUENCE:144
DTSTART;VALUE=DATE:20261102
DTEND;VALUE=DATE:20261103
SUMMARY:⚑ xAI: The grok-imagine-image-quality model name is retired from 
 the xAI API — and keeps answering\, served by a different model
DESCRIPTION:The grok-imagine-image-quality model name is retired from the x
 AI API — and keeps answering\, served by a different model\n\nMOVES TO: 
 grok-imagine-image-2.0 at low quality\, which the retired name silently re
 solves to after the date.\n\nBEFORE THIS DATE: Call grok-imagine-image-2.0
  explicitly before November 2 and choose the quality you pay for\; otherwi
 se the retired name keeps working but is served by a different model at lo
 w quality.\n\nCaveat: Nothing breaks on the date: 'The slug continues to r
 esolve\, so you do not need to change your code to avoid breakage.' What c
 hanges is the model behind the name and its price\, which xAI states is $0
 .01 per image lower at every resolution.\n\nAuthoritative document (xAI mi
 gration guide): https://docs.x.ai/developers/migration/imagine-image-quali
 ty-nov-2\n\nTracked by Hugin: https://hugin.studio/deadlines\nOnly dates a
  provider has published about its own product appear here.
URL:https://hugin.studio/deadlines
CATEGORIES:xAI\,retirement
TRANSP:TRANSPARENT
STATUS:TENTATIVE
BEGIN:VALARM
ACTION:DISPLAY
DESCRIPTION:xAI: Call grok-imagine-image-2.0 explicitly before November 2 a
 nd choose the quality you pay for\; otherwise the retired name keeps worki
 ng but is served by a different model at low quality.
TRIGGER:-P7D
END:VALARM
END:VEVENT
BEGIN:VEVENT
UID:openai-reusable-prompts-shutdown@hugin.studio
DTSTAMP:20260921T112823Z
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\nOnly dates a provider has pu
 blished about its own product appear here.
URL:https://hugin.studio/deadlines
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:20260921T112823Z
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\nOnly dates a provider has published about its own product appear her
 e.
URL:https://hugin.studio/deadlines
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:20260921T112823Z
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\nOnly dates a provider has published about its own product appear 
 here.
URL:https://hugin.studio/deadlines
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:20260921T112823Z
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\nOnly dates a provid
 er has published about its own product appear here.
URL:https://hugin.studio/deadlines
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:20260921T112823Z
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\nOnly dates a
  provider has published about its own product appear here.
URL:https://hugin.studio/deadlines
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-selfserve-finetuning-new-jobs-end@hugin.studio
DTSTAMP:20260921T112823Z
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\
 nOnly dates a provider has published about its own product appear here.
URL:https://hugin.studio/deadlines
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-legacy-audio-realtime-shutdown@hugin.studio
DTSTAMP:20260921T112823Z
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\nOnly dates a provider 
 has published about its own product appear here.
URL:https://hugin.studio/deadlines
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:20260921T112823Z
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\nOnly 
 dates a provider has published about its own product appear here.
URL:https://hugin.studio/deadlines
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:anthropic-claude-code-weekly-boost-end@hugin.studio
DTSTAMP:20260921T112823Z
SEQUENCE:3120
DTSTART;VALUE=DATE:20260913
DTEND;VALUE=DATE:20260914
SUMMARY:Anthropic: The 50% Claude Code weekly-limit boost ends
DESCRIPTION:The 50% Claude Code weekly-limit boost ends\n\nWHAT HAPPENED (f
 iled 2026-09-14 — Confirmed by this desk's own re-read):\nEnded at its s
 tated 11:59 PM PT on September 13\, when the terms article was rewritten 
 — and limits did not fall back: 'starting September 14\, 2026\, weekly l
 imits in Claude Code are 25% higher than they were before the promotion fo
 r Pro\, Max\, Team\, and seat-based Enterprise plans.'\n\nCaveat: Extended
  three times after its first stated end (July 13\, then August 19\, August
  31 and September 13)\; the terms article is the page that moved each time
 . The stretch between the first window's stated July 13 end and the July 1
 8 renewal has no provider-authored record and is carried at coverage tier 
 only.\n\nAuthoritative document (Claude Code May-August 2026 promotion ter
 ms): https://support.claude.com/en/articles/15910845-claude-code-may-augus
 t-2026-weekly-limits-promotion\nAnnounced in: https://x.com/ClaudeDevs/sta
 tus/2078511173759324328\n\nTracked by Hugin: https://hugin.studio/deadline
 s\nOnly dates a provider has published about its own product appear here.
URL:https://hugin.studio/deadlines
CATEGORIES:Anthropic\,promotional-window
TRANSP:TRANSPARENT
STATUS:CONFIRMED
END:VEVENT
BEGIN:VEVENT
UID:openai-gpt54-codex-signin-retirement@hugin.studio
DTSTAMP:20260921T112823Z
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\nOnly dates a pro
 vider has published about its own product appear here.
URL:https://hugin.studio/deadlines
CATEGORIES:OpenAI\,retirement
TRANSP:TRANSPARENT
STATUS:CONFIRMED
END:VEVENT
BEGIN:VEVENT
UID:anthropic-sonnet-5-intro-pricing-end@hugin.studio
DTSTAMP:20260921T112823Z
SEQUENCE:3308
DTSTART;VALUE=DATE:20260831
DTEND;VALUE=DATE:20260901
SUMMARY:Anthropic: Sonnet 5 introductory API pricing ($2/$10) ends
DESCRIPTION:Sonnet 5 introductory API pricing ($2/$10) ends\n\nWHAT HAPPENE
 D (filed 2026-09-14 — Confirmed by this desk's own re-read):\nReversed: 
 the introductory $2/$10 rate 'is now the standard price'\, and the page sa
 ys the 'previously scheduled increase to $3/$15 per million input/output t
 okens on September 1\, 2026 will not occur.' First found on September 1\; 
 unchanged on 2026-09-14.\n\nCaveat: Standard pricing of $3/$15 is stated f
 or September 1. These are the provider's published terms\, not a quote for
  any account.\n\nAuthoritative document (Pricing documentation): https://p
 latform.claude.com/docs/en/about-claude/pricing\n\nTracked by Hugin: https
 ://hugin.studio/deadlines\nOnly dates a provider has published about its o
 wn product appear here.
URL:https://hugin.studio/deadlines
CATEGORIES:Anthropic\,price-change
TRANSP:TRANSPARENT
STATUS:CONFIRMED
END:VEVENT
BEGIN:VEVENT
UID:openai-dalle-gpt-retirement@hugin.studio
DTSTAMP:20260921T112823Z
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\n
 Only dates a provider has published about its own product appear here.
URL:https://hugin.studio/deadlines
CATEGORIES:OpenAI\,retirement
TRANSP:TRANSPARENT
STATUS:CONFIRMED
END:VEVENT
BEGIN:VEVENT
UID:openai-assistants-api-shutdown@hugin.studio
DTSTAMP:20260921T112823Z
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\nOnly dates a provider has published about its o
 wn product appear here.
URL:https://hugin.studio/deadlines
CATEGORIES:OpenAI\,retirement
TRANSP:TRANSPARENT
STATUS:CONFIRMED
END:VEVENT
BEGIN:VEVENT
UID:openai-o3-chatgpt-retirement@hugin.studio
DTSTAMP:20260921T112823Z
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\nOnly dates a provider has published a
 bout its own product appear here.
URL:https://hugin.studio/deadlines
CATEGORIES:OpenAI\,retirement
TRANSP:TRANSPARENT
STATUS:CONFIRMED
END:VEVENT
BEGIN:VEVENT
UID:anthropic-cowork-doubled-limits-end@hugin.studio
DTSTAMP:20260921T112823Z
SEQUENCE:3254
DTSTART;VALUE=DATE:20260819
DTEND;VALUE=DATE:20260820
SUMMARY:Anthropic: Doubled Cowork 5-hour usage limits end and standard limi
 ts resume
DESCRIPTION:Doubled Cowork 5-hour usage limits end and standard limits resu
 me\n\nWHAT HAPPENED (filed 2026-09-14 — Not establishable by this desk):
 \nNot establishable. The terms article that carried the window has answere
 d HTTP 404 since August 20 and still did on 2026-09-14\; no replacement te
 rms article was found\, and the nearest help article describes how Cowork 
 uses limits without stating them.\n\nCaveat: A promotional window ending i
 s a return to standard terms\, not a reduction of anything anyone was enti
 tled to. The launch post still carries the superseded August 5 date\; the 
 terms article is the one that gets edited.\n\nAuthoritative document (Cowo
 rk promotion terms): https://support.claude.com/en/articles/15400594-claud
 e-cowork-june-2026-usage-promotion\nAnnounced in (still carries the supers
 eded date): https://claude.com/blog/cowork-web-mobile\n\nTracked by Hugin:
  https://hugin.studio/deadlines\nOnly dates a provider has published about
  its own product appear here.
URL:https://hugin.studio/deadlines
CATEGORIES:Anthropic\,promotional-window
TRANSP:TRANSPARENT
STATUS:CONFIRMED
END:VEVENT
BEGIN:VEVENT
UID:openai-chat-latest-api-shutdown@hugin.studio
DTSTAMP:20260921T112823Z
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\nOnly dates a provider has published about its ow
 n product appear here.
URL:https://hugin.studio/deadlines
CATEGORIES:OpenAI\,retirement
TRANSP:TRANSPARENT
STATUS:CONFIRMED
END:VEVENT
BEGIN:VEVENT
UID:openai-atlas-shutdown@hugin.studio
DTSTAMP:20260921T112823Z
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\nOn
 ly dates a provider has published about its own product appear here.
URL:https://hugin.studio/deadlines
CATEGORIES:OpenAI\,retirement
TRANSP:TRANSPARENT
STATUS:CONFIRMED
END:VEVENT
END:VCALENDAR