Codex Reset FAQ
A short guide to Codex usage limits resets, reset timing, Banked Resets, and forecast changes.
Check the latest reset card and recent reset history on the top page. If a reset was confirmed today, it should appear as a recent reset event. If there is only a forecast, treat it as an estimate rather than a confirmed reset.
OpenAI does not always publish an exact reset time. This site shows official notices and estimates whether a usage-limits reset looks likely within the next 24 or 48 hours.
Yes. On eligible plans, Codex and ChatGPT Work share the same agentic usage and credits pool. A reset affecting that shared pool can therefore affect both Codex and ChatGPT Work, although the applicable scope may vary by plan and event.
Not always. Even when an official notice describes a reset as applying broadly, the actual application can vary by plan or account conditions. We have seen past cases where Business was not included or was updated later. This site's history records the occurrence of reset events and does not guarantee that every plan received the reset in exactly the same way.
Not all ChatGPT usage limits are the same as Codex limits. On eligible plans, Codex, ChatGPT Work, and certain other agentic experiences share an agentic usage and credits pool. A reset affecting that shared pool can therefore affect both Codex and ChatGPT Work, while other ChatGPT limits may be separate.
A Codex reset usually restores or refreshes usage limits such as weekly limits or shorter usage windows. Some resets follow a regular cycle, while others may happen after incidents, capacity issues, or special events.
A Banked Reset is an account-specific reset available in your account. Using it refreshes the applicable usage limit. The resulting usage window and reset date may differ by account.
It means the Codex usage allowance or rate-limit window is refreshed. People may search for it as a token reset, limit reset, usage reset, or rate reset; this site groups those searches around Codex usage-limit recovery.
The forecast changes as the model combines past random-reset intervals, time since the last random reset, and current signals such as official notices, OpenAI Status incidents, capacity or rate-limit reports, and community activity. The percentage is not guaranteed and may move up or down.
It tracks Codex usage-limits reset notices, reset history, and random reset probability based on public information, community activity, and OpenAI Status updates.
It is a statistical reference for how likely a random reset may be within the next 24 or 48 hours. The model estimates how reset tendency changes with time since the last random reset from past random-reset intervals, then takes current observable signals such as official notices, OpenAI Status incidents, and community activity into account. It is not an official probability.
Teaser posts are treated separately from official notices. When wording such as tomorrow, tonight, a weekday, or a clock time can be resolved safely, the forecast reflects how much that hinted window overlaps the next 24 and 48 hours; for timed teasers, weak or strong hint strength is also used as an additional adjustment. If the timing cannot be resolved, the effect decays with the age of the post. A teaser is not a confirmed official schedule.
If there is an official notice, that takes priority. If there is no notice, this site shows the current estimate based on recent history and OpenAI Status activity.
People often use those terms loosely when searching. This site focuses on resets that restore or affect Codex usage limits.
A reset executed as compensation for incidents or issues. It may restore usage limits or grant additional Banked Resets to affected plans.
A special reset executed to celebrate milestones like user count achievements or product anniversaries.
A Hard Reset (Forced Reset) is a global, administrative reset executed by OpenAI for all users simultaneously. A Banked Reset (Manual Reset) is an account-specific reset that you can manually trigger whenever you choose.
Official notices are announcements by OpenAI or members of the Codex team (such as Tibo). Community signals are gathered from user reports and circumstantial evidence.
They are generally different concepts. While a local context reset affects session state, a usage-limit reset restores the usage allowance. However, they may occasionally overlap if context-related updates trigger a compensation reset.
While CLI issues affecting Codex usage limits or status updates are relevant, local CLI settings initialization or environment resets are outside the scope of this site.
It refers to confirmed past reset history, official developer notices, OpenAI Status API, and public community reports.
Using a Banked Reset refreshes the applicable usage limit. The resulting usage window and reset date may differ by account.