Your limit will come back. How it comes back depends on which of three things happened, and only one of them follows a rule you can compute.
That distinction is worth more than any reset-time estimate. People waste hours applying the wrong response to the right problem — waiting out a 5-hour window that will not touch a 7-day ceiling, or buying capacity they could simply have waited for.
If you already know which limit you are hitting and only want the fix, skip to what each usage error actually means. If the tool in question is Claude rather than Codex, the Claude-specific mapping is tighter. What follows is why the three kinds of reset behave differently from one another.
The short version
| Kind | Who decides | Can you predict it | Your move |
|---|---|---|---|
| Window release | Arithmetic | Yes, from your own usage | Work out when, then plan around it |
| Vendor reset | The vendor | No | Be told, as early as possible |
| Banked reset | You | You choose the moment | Spend it deliberately, never by accident |
Everything below is the reasoning behind those three rows.
1. Window release: the part you can compute
Codex constrains usage with two rolling windows rather than a daily quota. OpenAI's own documentation and in-product usage panel describe a short window measured in hours — commonly reported as 5 hours — and a longer 7-day window. The two are independent: clearing the short one does not restore the long one, and vice versa (OpenAI pricing and usage documentation).
The second window is the one people misread. When the short window looks healthy but you are still blocked, you are almost always on the weekly ceiling, and waiting 24 hours will not change that.
Because the windows roll rather than reset at a fixed hour, "when does it come back" is not a published number. It is a function of when you spent the capacity. The reset timestamp you see in a usage panel is sent by the vendor's servers with each usage report, not computed locally, so treat your own client's output as the live truth rather than a calendar rule.
The practical consequence: this is the only kind of reset worth doing arithmetic on, and the arithmetic is about your own history, not the vendor's schedule. It is also the only kind you can influence — see how to place your Codex window.
2. Vendor reset: the part nobody can compute
A vendor reset is a decision. Someone at the vendor decides to lift the cap early, and it applies to a group of accounts they choose. Recent examples are documented rather than hypothetical — OpenAI issued a global immediate reset to Plus, Pro and Business accounts on 7 September 2026, and the same help-centre article describes earlier rounds issued to eligible new and existing accounts on 3 and 4 September (OpenAI help centre: how banked Codex resets work).
Notice what is absent from that account: a schedule. There is no pattern to learn, because the trigger is a business decision — compute availability, a rough week, a model launch. A vendor reset is also the only event that changes your constraint without any action on your part, which is precisely why it is the one worth subscribing to a notification for.
Anything that claims to forecast these is guessing with confident typography. You can be told one happened. You cannot be told one is coming.
3. Banked reset: the part you decide
The newest of the three is a reset the vendor gives you but does not apply. It sits in your account until you spend it or it expires, and it is spent deliberately rather than automatically.
Two details about it are easy to get wrong:
- It refills both windows at once. Using a full banked reset resets the short window and the weekly cycle, and it changes your subsequent weekly reset date. That means spending it while you still have headroom wastes part of it and shifts your whole rhythm forward.
- Spending it is not always possible. It is consumed only if at least one eligible usage cycle is actually reset. If nothing can be reset, the banked reset stays in your account.
So this is not a fourth constraint to track. It is a decision you get to make once, and the only genuinely bad outcome is spending it by reflex on a day when the window would have refilled on its own within the hour.
The mistake all three invite
The three get conflated because they produce the same screen. A blocked request looks identical whether the cause is arithmetic, a vendor decision, or an unspent reset sitting in your account.
The order of checks that resolves it fastest:
- Does your usage panel show the short window refilling? Then you are on the weekly ceiling. Stop waiting, reorder the day.
- Does the panel show headroom but the tool still refuses? Check for an available banked reset before assuming a bug, then check the vendor's status page.
- Did the block lift with no action from you and no time passing? That was a vendor reset. Nothing you did caused it, and nothing you do will cause the next one.
That last point is the uncomfortable one, and it is why we built a notification rather than a calculator. A calculator can only work on the first of the three kinds — and the first is the only one you could have worked out yourself.
Worth separating out, because it changes which response is even correct: a speed-limit failure and an allowance failure are not the same thing, and only one of them is fixed by retrying. That is the subject of rate limits vs usage quotas.
FAQ
How long until my Codex limit comes back? If you are on the short window, capacity returns gradually as older usage ages out, so a partial recovery can arrive well before a full one. If you are on the weekly ceiling, only the week rolling forward or a vendor reset changes it.
Can anyone predict the next Codex reset? No. Vendor-issued resets follow a business decision, not a schedule, and OpenAI has never published one. Estimates you see online are reconstructions from past events, not forecasts.
Should I spend a banked reset as soon as I get one? No. Use it when you are actually blocked, or when a weekly ceiling is about to cost you a day of work. Spending it with headroom remaining resets your weekly cycle for no benefit.
Does clearing the short window help when I am on the weekly cap? No. The two windows are independent. The short window refilling restores nothing on the weekly side.
ResetRemind emails you when a confirmed reset lands for the plans you selected — Codex, Claude Code, Grok, Gemini. Free, no account, one click to unsubscribe.