{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreieexkowkgdzi6zst3x3vnp6lbl24mq5phhhj3ofz7atncbhjrwfl4",
    "uri": "at://did:plc:lk3jfj3zq4k4wxnk474axylu/app.bsky.feed.post/3mne3qmtfofq2"
  },
  "path": "/t/gpt-5-2-and-gpt-5-3-codex-have-been-sunset-in-codex-with-chatgpt-subscriptions/1382273?page=3#post_44",
  "publishedAt": "2026-06-03T02:03:39.000Z",
  "site": "https://community.openai.com",
  "textContent": "I wanted to share my genuine disappointment with the removal of GPT-5.3-Codex from the Codex platform as of June 2nd.\n\nWhile I understand the reasoning around fleet simplification, this change has a real impact on day-to-day usability — especially for Plus subscribers. GPT-5.5 consumes roughly 3× more reasoning time per minute than GPT-5.3-Codex, which means we’ve gone from ~60 minutes of usable reasoning time per session to just ~20 minutes. That’s not a minor tradeoff — it fundamentally changes how I’m able to use Codex for longer, more complex tasks.\n\nGPT-5.3-Codex struck a great balance between capability and efficiency. Forcing a switch to a model that burns through limits that much faster, without a corresponding increase in allocations, feels like a step backward for users who relied on it.\n\nI’d strongly encourage the team to either restore access to GPT-5.3-Codex, offer an opt-in for users who prefer it, or adjust reasoning time limits to compensate for GPT-5.5’s higher consumption rate.\n\nThank you for reading — I hope this feedback is taken into account.",
  "title": "GPT-5.2 and GPT-5.3-Codex have been sunset in Codex with ChatGPT subscriptions"
}