gpt-daybreak-red-latest
OpenAI has deprecated gpt-daybreak-red-latest but has not set a shutdown date yet. Replacement: gpt-5.6-cyber.
| Provider | OpenAI |
|---|---|
| Status | deprecated (an unpinned alias) |
| Shutdown date | not announced |
| Replacement | gpt-5.6-cyber |
| Source | https://developers.openai.com/api/docs/models/gpt-daybreak-red-latest |
| Note | alias (currently -> gpt-5.6-cyber). Model page says alias is deprecated; no shutdown date given |
Move off it before a date is set
- Find every call to it in your code (Python, JS/TS, Go, Java, configs, notebooks), with nothing to install:
uvx llmshift scan - Turn your real traffic into tests, so you compare on what your users send:
llmshift snapshot logs/ --model "gpt-daybreak-red-latest" - See exactly what changes on the replacement: formats, facts, tone, tool calls and settings it rejects:
llmshift compare --to gpt-5.6-cyber - Swap the model in your code and open a pull request with the results:
llmshift upgrade --from "gpt-daybreak-red-latest" --apply --compare --pr
Then llmshift init --github keeps the check on every pull request. LLMShift is free and open source (MIT) and runs on your machine.
Other OpenAI retirements
agent builder: retires 2026-11-30chatgpt-image-latest: retires 2026-12-01gpt-image-1-mini: retires 2026-12-01gpt-image-1.5: retires 2026-12-01gpt-image-1.5-2025-12-16: retires 2026-12-01gpt-5: retires 2026-12-11
Wrong date or replacement? Tell us on GitHub, with a link to the provider's page.
Lifecycle data updated 2026-11-14, collected from the providers' official deprecation pages. Dates can move: check the source before you plan around one. Visits are counted with GoatCounter, which sets no cookies.