{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreihvzlmlukzpx7y4ihlbkcylpsrg5ouzgdla23zialyomd7hgomg5e",
    "uri": "at://did:plc:lk3jfj3zq4k4wxnk474axylu/app.bsky.feed.post/3moh6iig5tba2"
  },
  "path": "/t/gpt-5-2-and-gpt-5-3-codex-have-been-sunset-in-codex-with-chatgpt-subscriptions/1382273?page=8#post_143",
  "publishedAt": "2026-06-17T01:05:50.000Z",
  "site": "https://community.openai.com",
  "textContent": "I’m a paying ChatGPT/Codex user and I relied on GPT-5.3-Codex for real development work.\n\nRemoving it from Codex Desktop/CLI for ChatGPT accounts broke my workflow. GPT-5.4 and GPT-5.5 are not equivalent replacements for my use case: GPT-5.3-Codex handled long end-to-end repo analysis with much better token/credit efficiency, while the newer models burn through usage much faster.\n\nPlease restore GPT-5.3-Codex as an optional selectable model, or provide a true low-cost Codex replacement with comparable coding reliability and token efficiency.",
  "title": "GPT-5.2 and GPT-5.3-Codex have been sunset in Codex with ChatGPT subscriptions"
}