{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreicm7gc4dqytyzn77s6n2lkhfgnopfq32o34f7x4vi6a4bdpmflggq",
    "uri": "at://did:plc:lk3jfj3zq4k4wxnk474axylu/app.bsky.feed.post/3ml2ebntq6ye2"
  },
  "path": "/t/gpt-5-5-codex-quota-drains-quickly/1380041#post_10",
  "publishedAt": "2026-05-04T18:12:37.000Z",
  "site": "https://community.openai.com",
  "textContent": "I’m seeing Codex in VS Code drain the 5-hour and weekly limits very quickly again around May 3–4.\n\nAfter the April 28 reset, usage felt reasonable for a few days, but now normal coding prompts are consuming quota much faster again. My workflow has not changed at all: same VS Code setup, same type of prompts, same coding tasks, and no unusually large refactors or intentionally long-running background tasks.\n\nSince I started using Codex, the 5-hour limit used to be enough for a real coding session. Now the same kind of work can consume the limit in about 1 hour, maybe 2 hours at most.\n\nThis issue started for me after the new Pro plan was introduced. From the user side, it feels like Plus limits may have been reduced or the quota accounting changed, because the same workflow now consumes much more of the 5-hour and weekly limits than before.\n\nPlease check whether there was a new regression or quota accounting change around May 3–4 involving VS Code Codex, GPT-5.5, Plan Mode, background sessions, retries, tool calls, or context refreshes.\n\nThe current usage meter does not show enough detail to know which task or session consumed the quota. It would really help to have a per-task/session breakdown and a clear explanation of how the 5-hour and weekly percentages are calculated.",
  "title": "GPT 5.5 Codex Quota Drains Quickly"
}