---
schema_version: "newruntime-agent-readable-v0.2"
type: "post"
stable_id: "post:codex-gpt-5-4-migration-boundary"
slug: "codex-gpt-5-4-migration-boundary"
title: "Codex Gets A Model Migration Deadline"
description: "OpenAI's ChatGPT and Codex changelog sets an August 31, 2026 cutoff for GPT-5.4 and GPT-5.4 mini in ChatGPT-signed Codex sessions, while keeping API-key paths available."
retrieval_nugget: "OpenAI's ChatGPT and Codex changelog sets an August 31, 2026 cutoff for GPT-5.4 and GPT-5.4 mini in ChatGPT-signed Codex sessions, while keeping API-key paths available. OpenAI added a small but operationally important Codex deadline: on August 31, 2026, GPT-5.4 and GPT-5.4 mini will no longer be available in Codex for users signed in with ChatGPT."
status: "published"
published_at: "2026-08-01"
updated_at: "2026-08-01"
record_date: "2026-08-01"
date_kind: "published_at"
topics: ["codex","models","developer-tools","operations"]
source_urls: ["https://learn.chatgpt.com/docs/changelog"]
visuals: [{"id":"codex-gpt-5-4-migration-boundary","kind":"editorial-diagram","role":"hero","src":"https://newruntime.com/images/posts/codex-gpt-5-4-migration-boundary.webp","alt":"Hand-drawn migration diagram where saved Codex defaults and scheduled tasks pass through a deadline gate into replacement model lanes while API-key sessions remain on a separate allowed path.","caption":"The GPT-5.4 cutoff is not a general disappearance; it is a boundary between ChatGPT-signed Codex defaults and API-key controlled sessions.","credit":"New Runtime synthesis from ChatGPT and Codex changelog","source_url":"https://learn.chatgpt.com/docs/changelog","generated_with":"gemini-3.1-flash-image","width":1600,"height":900,"legend":[{"label":"Deadline","description":"ChatGPT-signed Codex sessions lose GPT-5.4 and GPT-5.4 mini on August 31, 2026."},{"label":"Replacement","description":"OpenAI points GPT-5.4 users to GPT-5.6 Terra and GPT-5.4 mini users to GPT-5.6 Luna."},{"label":"API lane","description":"The OpenAI API and Codex sessions authenticated with an API key keep GPT-5.4 availability."}]}]
routes: {"html":"https://newruntime.com/posts/codex-gpt-5-4-migration-boundary/","markdown":"https://newruntime.com/posts/codex-gpt-5-4-migration-boundary.md","json":"https://newruntime.com/posts/codex-gpt-5-4-migration-boundary.json"}
source_format: "markdown"
---

# Codex Gets A Model Migration Deadline

## Retrieval answer

OpenAI's ChatGPT and Codex changelog sets an August 31, 2026 cutoff for GPT-5.4 and GPT-5.4 mini in ChatGPT-signed Codex sessions, while keeping API-key paths available. OpenAI added a small but operationally important Codex deadline: on August 31, 2026, GPT-5.4 and GPT-5.4 mini will no longer be available in Codex for users signed in with ChatGPT.

OpenAI added a small but operationally important Codex deadline: on August 31, 2026, GPT-5.4 and GPT-5.4 mini will no longer be available in Codex for users signed in with ChatGPT.

This is not a blanket retirement. The changelog says GPT-5.4 and GPT-5.4 mini remain available on the OpenAI API and in Codex sessions authenticated with an API key. The affected surface is the ChatGPT-signed Codex path, which is exactly where workspace defaults, saved model choices, managed configurations, custom agents, and scheduled tasks can silently carry an old model selection.

The recommended replacements are explicit: replace `gpt-5.4` with GPT-5.6 Terra, and replace `gpt-5.4-mini` with GPT-5.6 Luna.

The useful action is boring and immediate. Audit saved Codex defaults before August 31, especially any shared team config or scheduled task that does not get opened every day. A human choosing a model in the UI will notice a missing option. A saved agent configuration may only fail when work is already queued.

For New Runtime, this is another reminder that model routing is part of operations. A model name is not just a capability choice; it becomes config state, migration risk, and idempotency surface. The site already covered GPT-5.6 as API economics. This is the follow-through: after price-performance changes, the runtime still has to migrate old defaults without breaking stored workflows.