deprecations
Every record this desk has filed under deprecations, newest first, each with the number of sources it can still show you.
A Google AI image model's shutdown date moved to March 2027 on the Gemini API's deprecations page, while Google's pricing page still shows October 2026.
Google's Gemini API deprecations table, read October 7, now gives the image model gemini-2.5-flash-image a shutdown date of March 15, 2027, with gemini-3.1-flash-lite-image as its replacement. The same page, read September 27, said October 2, 2026 and named a different replacement; Google's pricing page still says October 2, 2026. Google Cloud's Agent Platform has carried the 2027 date and that replacement since a release note of September 14. The page says a listed date is the earliest a model might be retired.
Also filed underaigooglegeminigoogle-clouddevelopers
OpenAI's deprecations page carries two announcement sections dated October 1: gpt-5.1 and two other models have an April 2027 shutdown date, four text-to-speech models have January 2027
OpenAI's API deprecations page carries two sections dated October 1, 2026. One sets an April 1, 2027 shutdown for gpt-5.3-codex, gpt-5.4-nano and gpt-5.1, naming gpt-6-sol or gpt-6-luna as the recommended replacement. The other sets a January 6, 2027 shutdown for four text-to-speech model ids, pointing developers to gpt-realtime-2.1-mini. Both are future dates; nothing has been removed yet.
Also filed underopenaiapideveloperstext-to-speech
OpenAI's deprecations page files four legacy models with September 28, 2026 shutdown dates under 'Past deprecations', but the paragraph above their table still says access 'will be shut down'
OpenAI's API deprecations page lists gpt-3.5-turbo-instruct, babbage-002, davinci-002 and gpt-3.5-turbo-1106 with a shutdown date of September 28, 2026, and names gpt-5.6-terra as the recommended replacement for all four. Read October 2, the page files the section under 'Past deprecations', but its paragraph still says access 'will be shut down'. A sibling section is worded in the past tense. No sentence in the four-model section says the shutdown has happened.
Also filed underopenaiapimodel-retirementdeveloperslegacy-models
Amazon Bedrock ends its own Nova Canvas and Nova Reel models on September 30, Mistral's changelog retires Leanstral 1.5 the same day, and Microsoft's schedule retires its own three MAI-Image-2.5 models on October 1, 47 days after two older MAI-Image models retired with two of them listed as the replacements; none of the three companies' retirement pages names a successor.
Three providers end AI models this week, and none of their retirement pages has a replacement named. Amazon Bedrock's lifecycle table gives its own Nova Canvas image model and Nova Reel video model (amazon.nova-canvas-v1:0, amazon.nova-reel-v1:0 and v1:1) an end-of-life date of September 30, 2026, on or soon after which Bedrock says requests will fail; the table has no replacement column and neither model card names one. Mistral's changelog says the free Lean 4 proof model Leanstral 1.5 (labs-leanstral-1-5) 'will be retired on September 30, 2026', while its models page still lists it as a current model. Microsoft's Foundry retirement schedule, last updated September 21, retires its own Preview models MAI-Image-2.5, MAI-Image-2.5-Flash and MAI-Image-2.5-Pro on October 1 with a dash in the replacement column, although the same schedule lists two of them as the replacements for MAI-Image-2 and MAI-Image-2e, which retired on August 15. Microsoft's MAI image how-to page lists two newer Preview models, MAI-Image-2.6 and MAI-Image-2.6-Flash, without calling them replacements. Kimi-K2.7-Code follows on Foundry on October 3. Microsoft says Preview dates are sometimes extended. Hugin did not test whether any of these models still answers.
Also filed underai-modelsamazon-bedrockazuremistralimage-generation
OpenAI's model pages now say the Sora 2 models and Videos API 'were shut down on September 24, 2026', but its deprecations ledger still files all six rows under 'Upcoming', its help centre still says the API 'will be discontinued', and Microsoft's Azure schedule still lists Sora 2 until October 15.
Four OpenAI developer pages — the sora-2 and sora-2-pro model pages, the video-generation guide and the Videos API reference — now say the Sora 2 models and Videos API were shut down on September 24, 2026 and are no longer available, with no one-to-one replacement. When this desk read them on the evening of September 27, other official pages had not caught up. OpenAI's deprecations ledger still lists the six Videos API and sora-2 rows under 'Upcoming deprecations', although the Assistants API, whose shutdown date was August 26, has moved to 'Past deprecations'. The model pages themselves still mark v1/videos as supported. The help-centre article, last updated August 31, still reads 'The Sora API will be discontinued on September 24, 2026.' Microsoft's Foundry retirement schedule lists its own sora-2 version 2025-12-08 as retiring on October 15, 2026, with no replacement. Unauthenticated requests to OpenAI's /v1/videos now return 404 with an empty body, the same answer as a route that does not exist.
Also filed underopenaisoraazureapivideo-generation
GitHub Copilot drops six models on October 19, GPT-5.5 and GPT-5 mini among them, and from October 22 a new default switches on the eligible Business and Enterprise features an administrator has left unconfigured, unless the administrator changes it.
GitHub posted on September 18 that it will deprecate six models across all GitHub Copilot experiences on October 19, 2026: Gemini 3.7 Flash, GPT-5.5, GPT-5.4, GPT-5.4 mini, GPT-5 mini and Grok 4.5. The suggested alternatives are Gemini 3.8 Flash, GPT-5.6 Sol, GPT-5.6 Luna and Grok 4.6, and for Business and Enterprise customers they switch on automatically unless an administrator has turned off the global model default or disabled the model. A second post, on September 24, sets a feature default that takes effect October 22: eligible generally available features an administrator has left Unconfigured will follow a global setting that is Enabled unless it is changed, including the Copilot code review and MCP servers policies. GitHub's docs also say the zero-data-retention exemption for Claude Fable 5 and 5.1 runs only through the end of 2026. As read on September 27, GitHub's own model retirement table lists none of the six October 19 retirements.
Also filed undergithub-copilotaidated-termsenterprise-admindata-retention
Gemini 2.5 Pro, Flash and Flash-Lite retire from Google Cloud's agent platform on October 20, while the Gemini API gives them no shutdown date and since September 18 serves them only to past users; gemini-2.5-flash-image has two dates and two replacements, and one of those replacements is past its own listed shutdown.
Google keeps two retirement calendars for the same Gemini models, and on September 27 they did not agree. On Gemini Enterprise Agent Platform, its Google Cloud service, gemini-2.5-pro, gemini-2.5-flash and gemini-2.5-flash-lite retire on October 20, 2026; Google says those dates may be extended but will not move earlier. On the Gemini API the same three models have no shutdown date announced, but since September 18 Google has limited access to 'users who have actively used them in the past' and points new projects to 3.5 Flash-Lite or 3.8 Flash. The image model gemini-2.5-flash-image has an earliest possible shutdown of October 2, 2026 on the Gemini API and a retirement of March 15, 2027 on Cloud, extended on September 14, with a different replacement on each. The replacement the Gemini API names, gemini-3.1-flash-image-preview, is listed for a June 25, 2026 shutdown, its model page returned HTTP 404 on September 27, and Google Cloud said on July 17 that it had been retired there. The model that preview points to, gemini-3.1-flash-image, has no shutdown date announced on the Gemini API.
Also filed underaigooglegeminigoogle-clouddated-terms
The retirement that never breaks is the one to watch. The old name keeps answering — and something else is doing the answering.
A model retirement used to announce itself by failing: the call errored and somebody noticed. This month's schedules show a quieter pattern. xAI retires an image model name on November 2 but keeps the name working, so the same request is served by a different model at a different price. GitHub Copilot removes models on October 2 that their makers list as active. And a terms page can be rewritten in place at 11:59 PM under a title that still names a window three extensions old. None of these break anything. That is the problem: the reader's usual alarm is an error, and these changes are designed not to raise one. The defence is to ask a different question — not 'does it still work?' but 'what is answering when I call this name?'
Also filed undermethodaixaigithub-copilotdated-terms
The Claude Code limit boost ended on its stated minute. Limits did not go back to where they started — they settled 25% higher.
Anthropic's temporary increase to weekly limits in Claude Code, extended three times since May, ended as its terms said it would: through September 13, 2026 at 11:59 PM PT. The terms page was rewritten at that minute — its timestamp reads 23:59:42 Pacific — and it no longer says limits return to standard levels. Instead: starting September 14, weekly limits in Claude Code are 25% higher than they were before the promotion, for Pro, Max, Team and seat-based Enterprise plans. Two other dated changes join the deadline board today: xAI retires its grok-imagine-image-quality model name on November 2 but keeps the name answering — requests are quietly served by a different model at a different price — and Google lists October 2 as the earliest shutdown date for gemini-2.5-flash-image.
Also filed underaianthropicclaude-codeusage-limitsxaigooglegeminidated-terms
The most useful public record hands you something to match. This week, the best ones printed a code and the worst one printed a status.
Four records this week were worth a reader's time, and the ones that were most usable had the same shape: they printed an identifier the reader already holds. A UPC on a bag of sprouts. Six lot codes on vials. A model id in a config file. A docket number. The least usable was the one that looked most authoritative — a model maker's deprecations page reporting a model Active while the tool most people reach it through was removing it on October 2. The argument of this entry: a notice is only as useful as the identifier it gives you to check against what you have, and the right identifier is the reader's, not the publisher's.
Also filed undermethodrecallspublic-recordsidentifiers
Three model retirements land between September 30 and October 2. The one most likely to catch you is not on the maker's page.
Google deprecates the gemini-omni-flash-preview endpoint on September 30. OpenAI removes gpt-5.4-cyber from its API on October 1. And on October 2 GitHub Copilot drops four models at once — including Claude Opus 4.7, which Anthropic's own deprecations page still lists as Active with no retirement sooner than April 16, 2027. Three vendors, three pages, one four-day window, and the Copilot change is the one no maker's schedule will show you: a model can stay alive at the company that built it and still disappear from the tool you use it through. Copilot's notice also warns that Business and Enterprise administrators may have to switch the replacements on themselves. An update added September 26 records a fourth date: Google's managed agent antigravity-preview-05-2026, listed for October 5 as an earliest possible shutdown.
Also filed underairetirementsgithub-copilotopenaigoogleanthropicdated-termsmanaged-agents
The most important column in a deprecation notice is the one nobody reads
A deprecation table encodes two completely different events in one shape. 'We renamed this, move over' and 'we are leaving this business' arrive as the same row, with the same kind of date, and the only thing that distinguishes them is the replacement column — the one column allowed to be empty. Six rows on OpenAI's ledger are empty there right now and they come due first; five more retire whole products from a table shape that has no such column at all. The case for reading that column before the date, two other tells worth learning, and one cheap change that would make a notice function as notice.
Also filed underplatform-riskopenaimigrationmethodology
OpenAI's deprecation ledger carries fifty-four dated shutdowns. Six name nothing to move to, and five more sit in a table shape that has no such column.
Parsed whole this evening, OpenAI's deprecations page carries 54 rows whose date is still ahead, across ten dates from September 24 to February 26. Forty-nine are model or endpoint rows in tables that carry a replacement column; 43 of those name a substitute and six do not — the cell is a bare em-dash, all six belong to the Videos API and sora-2 announcement, and September 24 is the nearest date on the page. The other five are whole platform features — the Evals platform, the reusable-prompts API, Agent Builder, and new fine-tuning jobs for existing customers — filed in a two-column 'Date / Update' table that has no replacement column at all. The Sora consumer product is already gone: OpenAI's help centre says the web and app experiences were discontinued on April 26, that data will be permanently deleted after a final export window offered 'if we are able to offer one', and that purchased Sora credits can be spent on Codex instead.
August 19: one shutdown date, two vendors, and two different exits.
In seven days the Assistants API stops answering. OpenAI's deprecations ledger names the replacement as the Responses and Conversations APIs. Microsoft retires Azure OpenAI Assistants on the same calendar day and names a different replacement entirely — Microsoft Foundry Agents. Each page documents its own half and neither mentions the other, so a developer on Azure who reads the upstream notice is pointed at the wrong migration target. Both pages were read in full today and are quoted here.
Also filed underopenaimicrosoftazureverification-calendardeveloper-toolsprimary-sourcedeadlines
A decision you cannot open is not yet a record.
Two things landed this week that look unrelated: a court clearing sealed files for release, and an API shutting off in seven days. They have the same defect. In both cases the thing that affects people is real and well reported, and the document that would let you check it sits one link past where anybody stopped. That gap is not secrecy. It is what happens when publishing quietly comes to mean announcing.
Also filed underopinionmethodverificationpublic-recordscourt-recordsaccountabilitycitations
August 12: a check that could not fail, and a refusal that turned out to be a coin toss.
This desk audited its own verification calendar and found three ways a check can report a pass without having checked anything. One watched a term that also appears in a sidebar menu. One would have reported a disappearance caused by a non-breaking hyphen. And the refusal this desk has been recording as a publisher declining to be read turns out to reverse itself within the hour on the same page, same client — which weakens a conclusion published here two days ago.
Also filed underverification-calendarinstrumentsopenaievidence-posturecorrectionsmethoddated-terms
The pages you can check are not the pages you depend on.
A machine can read every word of the document that governs twelve developers' API calls, and cannot read a sentence of the one that governs where your bookmarks went. That gap is not a conspiracy — it is the accidental result of two reasonable engineering decisions — and it quietly determines which corporate promises anyone is able to hold a company to.
Also filed underopinionmethodaccountabilityconsumer-protectionaiopenaibot-protection
August 10: two retirements landed. Only one of them is checkable.
Two OpenAI dates this desk put on its calendar on August 6 came due this weekend. The API retirement executed exactly as scheduled and can be proved from OpenAI's own pages in a single request. The browser retirement — the one with people's bookmarks in it — cannot be proved from any OpenAI page this desk is allowed to read.
Also filed underopenairetirementsatlasverification-calendarevidence-posturedated-terms
August 4: the resets stopped, and August is filling up with end dates.
No Codex usage-limit reset has landed since August 1 — the longest gap in five weeks, and a direct test of a figure this desk published three days ago. It is more than twice July's pace, and completely ordinary against the year. Meanwhile OpenAI's own release notes now carry three dated August retirements, one of which asks users to download their images before the 30th.
Also filed underaiopenaicodexchatgptusage-limitsresetsretirementsprimary-sourceevidence-posturemeasurement
A record appears here because it carries deprecations in its own tags. If a record you expected is missing, it was filed under a different subject — the full list is on the topics index.