{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreiemba73g4ym7777hpylrdqx5l3w7rettmx6sysr4tamz2ufaqa4bu",
    "uri": "at://did:plc:lk3jfj3zq4k4wxnk474axylu/app.bsky.feed.post/3mlviar5ldyu2"
  },
  "path": "/t/codex-usage-limits-seem-to-be-draining-unusually-fast-since-10-may-2026-even-with-light-gpt-5-3-codex-use-while-the-usage-tracking-ui-also-appears-buggy-or-missing/1380649#post_8",
  "publishedAt": "2026-05-15T13:08:26.000Z",
  "site": "https://community.openai.com",
  "textContent": "I think there’s an important misunderstanding here regarding the limits.\n\nThe “5h limit” is not a limit where you can use Codex for only 5 hours per day. It’s actually a token/computation quota measured over a rolling 5-hour window.\n\nI initially misunderstood it the same way, especially because it’s displayed next to the weekly quota, which makes it look like a time allowance rather than a usage window.\n\nI’m not entirely sure why OpenAI chose this system, but my guess is that Codex enables extremely heavy workloads compared to normal chat usage. With the recent promotional/free-access period, a huge number of users probably started running very intensive coding sessions simultaneously.\n\nThat likely created enormous compute demand on the servers, especially since Codex tasks can consume far more resources than standard conversations.\n\nI do agree that labels like “daily limit” and “weekly limit” would probably be clearer and less confusing for most users, though.\n\nHope this clears things up a bit.",
  "title": "Codex usage limits seem to be draining unusually fast since 10 May 2026, even with light GPT-5.3 Codex use, while the usage-tracking UI also appears buggy or missing"
}