When Does Codex Reset? How to Track Your Real Limit Window
If you are asking “when does Codex reset?”, the shortest accurate answer is: there is not one universal reset clock that applies to every situation. In practice, most users are dealing with at least three different things: their own 5-hour window, their own weekly window, and occasional global reset announcements that OpenAI may push for broader groups of users. The reason a site like codex-reset.com is useful is that it separates those ideas instead of treating them like one timer.
That distinction matters because OpenAI's official help pages explain plan access, shared usage pools, and credit behavior, but they do not turn the whole experience into a simple reader-facing workflow. If you are trying to decide whether you can keep working now, whether you should wait, or whether a global reset post actually changed your account state, you need a more operational explanation than “limits vary by plan.”
The main mistake people make
The most common mistake is assuming every mention of a “Codex reset” means the same thing. It does not. Sometimes people are talking about their own rolling usage window. Sometimes they mean a public goodwill reset announcement for paid users. Sometimes they mean a banked reset that can be applied later. And sometimes they are just reacting to the fact that usage went down faster than expected because a heavier task, larger codebase, or more expensive model consumed more of the shared allowance.
OpenAI's current help documentation says Codex is included across ChatGPT plans, with limits and credit options varying by plan, and it also says usage from Codex and other eligible agentic surfaces can draw from the same shared pool. That means the question is not only “when does Codex reset?” but also “which limit am I actually looking at right now?”
The four reset concepts you should separate
| Concept | What it means | What should confirm it |
|---|---|---|
| Your 5-hour window | A personal rolling window tied to your own usage state, not a universal global timestamp. | Your own Codex usage page, limit banner, or client-specific status output. |
| Your weekly window | A longer personal reset window that can move when a broader reset changes the next cycle anchor. | Your own account UI and current usage banner. |
| Global goodwill reset | A wider reset or limit event announced for many users at once. | Official or near-official announcement plus actual account reflection. |
| Banked reset | An extra reset that may be stored and applied later rather than happening immediately. | Your own usage summary or reset inventory when the plan or promotion supports it. |
Once you separate those four ideas, the topic gets much easier. Your own access is always controlled by your own current account state. A public announcement can explain why that state changed, but it is not the same thing as your personal clock.
What OpenAI officially confirms
The official baseline comes from OpenAI, not from social posts and not from third-party trackers. The current help article on using Codex with your ChatGPT plan says Codex is available across ChatGPT plans, while usage limits and credit options vary by plan. The same article also says that usage from Codex, ChatGPT Work, ChatGPT for Excel, and Workspace Agents can draw from the same agentic usage and credit pool when those features are available on your plan.
That one point explains a lot of the confusion. Users often think they are tracking a single isolated Codex timer, when in reality they may be consuming from a broader shared pool. OpenAI also says the amount a Codex task uses depends on the size and complexity of the work, the model, and where the task runs. So if you are trying to interpret a sudden drop in remaining allowance, a heavy task can matter just as much as the passage of time.
The second official page that matters here is the Codex rate card. It explains that Codex usage is accounted for with token-based pricing, using input, cached input, and output tokens. That means the phrase “5-hour limit” should not be read like a promise of five hours of uniform interactive coding time. A short, light task and a long, high-context task do not consume the pool the same way.
That does not mean users are wrong to want clearer reset tracking. It means the official rule set is about plan access, shared pool behavior, and token consumption, while the user problem is operational timing: “Do I actually get to keep working now, and if not, when does that change?”
What codex-reset.com adds that the official docs do not
This is where codex-reset.com becomes useful. Checked on July 25, 2026, the homepage explicitly separates personal 5-hour and weekly clocks from global goodwill resets. Instead of pretending it knows your private account state automatically, it tells you to enter the exact timestamps from your own client output and keep those personal clocks local to your browser.
That is a good design decision. It avoids the false promise that a public website can know your exact next unlock without your own account data. In other words, the site's value is not that it replaces OpenAI's own usage surfaces. Its value is that it gives users a place to organize the moving pieces without confusing public signals for private state.
The second required page is the verified reset timeline. That page is useful because it states a method: announcement time is shown unless a later effective time is independently verified, and preview windows are not backfilled as actual arrival times without source proof. That methodology is exactly what readers need, because many people wrongly assume an announcement timestamp and a personal reset timestamp are interchangeable. They are not.
How to tell which reset matters to you right now
If your actual question is practical rather than theoretical, use this sequence.
First, check your own usage surface before checking social chatter. If your usage page or limit banner still says you are capped, that is the truth that matters for the next few minutes. A public announcement may explain a change that is propagating, but it does not override what your own account is currently showing.
Second, decide whether you are dealing with a personal timer or a public event. If the UI is showing a countdown tied to your own recent usage, you are looking at a personal window. If you are seeing people talk about “everyone got reset” or “limits were restored,” that is a public event claim that still has to meet your own account state before it becomes operationally real for you.
Third, use codex-reset for the job it is actually good at. If you want a cleaner record of public reset announcements, time-zone normalization, and a distinction between previews and verified arrivals, the timeline is useful. If you want your own next personal unlock, use your own usage page and, when your client supports it, the exact timestamp output the site asks you to paste into its local tracker.
Fourth, do not forget the shared-pool rule. If you are using multiple eligible agentic surfaces under the same plan, a change in remaining usage is not always caused by a “Codex-only” event. OpenAI's own help documentation says those surfaces can share the same pool. That is one of the easiest ways to misread what happened.
When a global reset announcement still does not answer your question
A global reset announcement can be real and still not fully answer the question you care about. Suppose a public post says paid users received a reset. You still need to know at least three things: whether your plan is in scope, whether the reset applied immediately or was previewed for later propagation, and whether your next personal weekly window anchor changed after the reset. Those are not trivial details, and they are exactly why users keep opening community threads about changed dates and missing banked resets.
That does not mean the tracker is wrong or the official docs are incomplete in a careless way. It means they solve different layers of the same problem. OpenAI documents product rules. codex-reset documents public reset signals and gives you a better way to keep your own timestamps organized. You need both layers if you want less confusion.
What this means for teams, not just individual users
This topic is not only a solo-user problem. Teams get tripped up by it too. A manager might see a public “reset for everyone” announcement and assume the team can resume heavy work immediately. An engineer might assume a fresh weekly window means no shared-pool pressure from other surfaces. Both assumptions can be wrong.
The safer operating model is simple: treat official product docs as the rulebook, treat your account UI as the immediate source of truth for what you can do now, and treat a tracker like codex-reset as the historical and workflow layer that helps you interpret broader events. That model is much more useful than waiting for one magic answer to “when does Codex reset?” because there usually is not one.
Should you rely on codex-reset.com?
Yes, but for the right scope. It is useful if you want a cleaner explanation of public reset history, a way to separate public events from private timers, and a simple personal log for your own exact reset timestamps. It is not a replacement for OpenAI account surfaces, and it should not be treated like a privileged backend view into your plan.
That balanced position is what makes the site practical. It does not claim to be the authoritative ledger for your account. It gives users a better mental model and a lighter workflow. For this topic, that is real value, because confusion is the entire problem.
The bottom line
If you only remember one thing, remember this: “Codex reset” is not one clock. Your personal 5-hour and weekly windows are yours. Public goodwill resets are broader events. Banked resets are yet another layer. OpenAI's own pages explain the shared usage pool and credit mechanics, while codex-reset.com helps you track the messy public side without pretending it owns your private account state.
So the right question is not just “when does Codex reset?” The better question is “which reset am I looking at, and where should I verify it?” Once you ask that, the answer becomes much more actionable.
