Noesa
← The Casebook

Global · March 2023

The code model thousands had built on was announced dead on a Monday and gone by Thursday.

OpenAI retired the Codex API three days after announcing it. Nobody could keep a copy — and the same vendor now promises six months' notice, for a tier Codex was never on.

Published 2 September 2026

What happened

OpenAI's Codex models were the first widely available systems for turning English into working code, and by early 2023 they sat underneath a large number of developer tools, side projects and published research. They had been free the whole time, in a limited beta with heavy rate limits [2].

On 20 March 2023 OpenAI announced that `code-davinci-002`, `code-davinci-001`, `code-cushman-002` and `code-cushman-001` were being retired. The shutdown date was 23 March 2023 — three days later [1].

Users were told to move to GPT-3.5 Turbo, the model then powering ChatGPT, which OpenAI said would improve programming results [2].

The difficulty was not the replacement but the exit. Codex was never downloadable and could not be self-hosted; access existed only through the API, so when the API closed the model was simply gone, with no way for anyone outside OpenAI to preserve a copy [2].

That hit published research hardest: studies built on Codex could no longer be reproduced or extended, because the object they measured had ceased to exist [2]. After the reaction, Sam Altman said researchers would keep access — "We didn't realize how much people liked this model; we will continue to support it for researchers!" [2].

Simon Willison, writing the day after the announcement, called it a major strategic misstep, arguing that the damage was less to any one project than to confidence in OpenAI as a stable platform to build on, at a moment when competitors and open-weight alternatives were arriving [3].

OpenAI's deprecation policy today promises minimum notice before a model is retired — at least six months for generally available models, unless safety or compliance forces a faster timeline. Codex was a free beta rather than a generally available product, and it got three days [1].

Where it helped

The retirement itself was defensible, and the honest version of this case says so. Codex was a free research beta that had run over a year past its welcome, its replacement was genuinely better at the task, and a vendor that can never retire anything ships nothing. OpenAI also publishes a deprecations page with dates and replacements — most vendors do not, and that page is why this case can be sourced to the record rather than to recollection [1][2].

Where it burned

Everything downstream had been built on the assumption that the substrate would still be there next week. The people affected had made a reasonable-looking decision — use the best available model — and an unexamined one: they had no copy, no equivalent alternative they had actually tested, and no idea what notice they were entitled to, because they had never asked. Free was the tell they missed. Nothing was breached and nothing was inaccurate; the thing simply stopped, and reproducing a published result became impossible for reasons that had nothing to do with the research [2][3].

The tell

Before you build on a model you cannot keep a copy of, find out what notice you are owed when it goes away — and which tier of the vendor's promise you are actually on. Free and beta usually means none.

Every other check in this Casebook asks whether to believe an output. This one asks whether the thing producing outputs will be there in six months, which is a different kind of risk and fails in a different way: not wrong answers, but no answers, on a date you did not choose. The questions are cheap and worth asking before you commit rather than after. Can I run this myself, or export what it produced in a form something else can read? What is the published deprecation notice, and does my plan qualify for it? Have I actually run my work against a second option, or merely assumed one exists? A dependency you could replace in an afternoon is a tool. One you could not is a business partner you never negotiated with.

Share this case

The image has the link printed on it, so it still leads back here.

The check is a habit, and habits are trained. System design, understood is about the dependencies you take on and what happens when one of them disappears — the difference between a component you chose and a component you are stuck with.

Sources

Every source below was opened and read. Last verified 2 September 2026.

  1. [1] Deprecations — Codex models, and the model retirement notice policyOpenAI (API documentation), announced 20 March 2023; shutdown 23 March 2023
  2. [2] OpenAI kills its Codex code model, recommends GPT-3.5 insteadThe Decoder, March 2023
  3. [3] OpenAI to discontinue support for the Codex APISimon Willison, 21 March 2023