Codex Quota Limits: 5-Hour vs Weekly Windows, Reset Types & Recovery Guide
This guide explains Codex's dual quota system (5-hour and weekly windows), details how limits vary by subscription tier (Plus, Business Standard, Pro), and covers four recovery methods: natural refresh, saved resets, automatic resets, and paid instant resets, with practical advice for developers managing project workflows during quota exhaustion.
Distinguishing the 5-Hour and Weekly Limits
Codex quota limits operate on two independent windows: a 5-hour rolling window and a weekly window. Both apply simultaneously to Plus and Business Standard plans for Work and Codex usage; hitting either limit blocks further requests until that window refreshes. The 5-hour window is not a fixed request count — consumption varies by model, input size, and task steps.
Pro 100, Pro 200, and Pro 500 plans currently do not have a 5-hour window ; they only have a weekly included quota. Regular Chat message limits are separate and cannot be used to infer Codex availability.
Open Settings → Usage to see the current logged-in identity, workspace, remaining quota for each window, and the next refresh timestamp. If only the 5-hour window is exhausted, waiting for its natural refresh works; if the weekly quota is also exhausted, the 5-hour refresh will not restore access. Always rely on the times shown in the UI.
Natural Refresh: Most Reliable but Easily Misunderstood
The 5-hour window starts from the first Work or Codex request after the previous window ended; the weekly window follows its own cycle. Their end times do not necessarily align. Closing the client, re-logging, or switching models does not trigger a refresh; the shared quota pool is model-agnostic.
If the numbers appear stale, refresh the Usage page and verify the workspace. Quota recovery does not restore project files — commit changes, record branches and TODOs before the window closes so work can resume cleanly.
Saved Resets: Check Before You Click
Eligible users may receive a one-time "Saved Reset" from specific promotions. It does not auto-apply. On desktop, check Settings → Usage & Billing ; on web, view Usage settings. If a reset is available, review its coverage scope and expiry before redeeming. The Codex CLI command /usage (in supported versions) may also surface a redemption entry.
A full Saved Reset restores the main Codex quota per plan: Plus and Business Standard regain both 5-hour and weekly quotas; Pro tiers regain weekly quota. It does not replenish image-generation limits or add credits. Redemption requires at least one covered quota to be below 80% remaining; otherwise the reset stays banked until used or expired. Another user's available reset button is not your guaranteed entitlement.
Automatic Resets vs Paid Instant Resets: Not the Same Thing
Automatic resets are granted directly by OpenAI for specific campaigns — no redemption needed, and they do not appear in "Available Resets." They apply only to the campaign's designated users and quotas; do not assume they recur regularly.
Paid instant resets are offered to select individual Plus and Pro subscribers. If a purchase banner appears, verify the price, coverage, and cycle details. It immediately advances the current week's Work and Codex included quota; the new weekly cycle begins at the next request after purchase. The reset cannot be saved for later and does not add credits. When only the 5-hour limit is hit, a weekly-quota purchase banner may not appear.
A common pitfall: a reset changes the next refresh time for affected quotas but does not alter the subscription billing date . After a weekly window opens early, the old "refresh next Friday" mental calendar becomes invalid. Check the updated Usage page timestamps instead of relying on the old schedule. If a purchased reset doesn't reflect in the numbers, locate the receipt, refresh the Usage page, then follow official support channels — do not repurchase to test.
Choosing a Strategy When Deadlines Loom
Recommended decision flow: (1) Identify which limit type is hit and its refresh time. (2) Check for any usable Saved Reset. (3) Compare waiting, eligible credits, reducing task scope, and upgrading costs. Break long tasks into verifiable small steps — read key files first, then proceed based on test results — rather than re-running the entire repo repeatedly.
Credits and resets are distinct: credits fund eligible features on a pay-as-you-go basis; resets refresh the plan's included quota. Availability depends on the current plan and UI. Short-term crunches can justify a one-off cost; sustained high usage should be evaluated against actual weekly consumption, not a single promotional event.
What recovers is the officially permitted quota window, not a workaround to bypass limits. Project progress still depends on solid version control.
Signed-in readers can open the original source through BestHub's protected redirect.
This article has been distilled and summarized from source material, then republished for learning and reference. If you believe it infringes your rights, please contactand we will review it promptly.
How this landed with the community
Was this worth your time?
0 Comments
Thoughtful readers leave field notes, pushback, and hard-won operational detail here.
