Codex Usage Limits Reset: Official Methods, Reset Types, and Scam Avoidance

Identify Which Usage Window Is Blocking You

Open ChatGPT or Codex Settings → Usage and note the remaining quota and the next refresh timestamp. For Plus subscribers, Work and Codex share the same plan quota and currently have two concurrent windows: a 5-hour window and a weekly window. Both must have remaining allowance for tasks to proceed; if one window refreshes but the other is still exhausted, the limit remains. Pro 100, 200, and 500 tiers do not have a 5-hour window for Work/Codex but still include usage quota — do not apply Plus tutorials directly to Pro.

Normal Cycle Refresh is the simplest: wait until the time shown on the page arrives. The 5-hour window starts counting from the first request after the previous window ends; the weekly window follows the UI indication. Do not rely on mental calculation. Reinstalling the app, switching devices, or clearing conversations will not generate new plan quota.

Gifted Resets: Banked and Automatic Are Not the Same

OpenAI may grant some users a banked reset (shown as "banked reset" on English pages). This is a one-time entitlement that appears in the available list when received. Before using it, check its expiry date and which windows it covers. On desktop, open Settings → Usage & Billing or the web usage settings; if an available reset shows, open its summary, verify the applicable scope, then confirm use. The mobile app currently has no entry point for this action.

A banked reset cannot be used at any arbitrary moment: at least one covered quota on the usage page must be below 80% remaining. The full entitlement for Plus covers both the 5-hour and weekly main quotas; for Pro (all three tiers) it covers only the weekly main quota. Windows that are already full will not restart. After a successful reset, the next refresh time of the affected window may change — it does not stack an extra cycle on top of the old one.

The other type is an automatic reset : OpenAI applies it directly to the selected usage scope without manual claiming, and it does not appear in your available balance. It is not a fixed benefit for every user, and receiving a notification about someone else's automatic reset does not guarantee you will get one.

Paid Instant Reset and Credits Serve Different Purposes

Eligible individual Plus and Pro users may see a purchase instant reset option in usage settings, or a prompt when the weekly quota is exhausted. Whether it appears depends on the current login identity, plan, and region; simply subscribing to Plus or Pro does not guarantee the entry point. If you only hit the 5-hour limit, the "weekly exhausted" prompt may not show; check the desktop usage settings first instead of seeking third-party operators.

Before purchasing, read the displayed price and remaining quota. The instant reset takes effect immediately after the transaction completes — it cannot be bought in advance and stored. It pulls the applicable weekly usage cycle forward to now; the next normal weekly refresh will count seven days from the first subsequent Work/Codex request. It does not increase credits, nor does it add an extra weekly quota permanently. If a natural refresh is imminent, decide based on the urgency of your own pending tasks.

Credits are a separate mechanism : in eligible features, after the included usage is exhausted, consumption can be deducted from the credit balance per unit of usage. Credits are not equivalent to a window reset and do not enable every model to continue. Compare the interface's stated coverage, price, and your actual task volume — do not treat "buying credits" as an unlimited refill.

Final Safeguards

After using an entitlement or completing a purchase, the usage display may need a brief moment to update; refresh the page and verify the login identity, workspace, and the specific window. Do not purchase again just to test. If the quota still appears incorrect, contact official support with the timestamp, receipt, and UI prompts. Support can investigate metering issues or restore anomalies but cannot manually raise limits for users. Commit or save your code changes first, then resume from a small, verifiable task once the quota recovers — technical execution must be grounded, and choices must be clear-headed.