CODEX FIELD NOTES
When is the next Codex reset? What the history can tell you
Understand the 6.9-day historical average, the long gaps behind it, and why an estimate is not an official schedule.
By codex resets editorial team · Updated · 2 min read
There is no guaranteed public reset timetable. The next-reset page shows the current estimate and original evidence. Your account's personal renewal time remains in Usage.
Count events rather than posts
A preannouncement and a later completion can describe the same reset. The archive groups related posts into one event, while preserving their original text. Replies cannot create independent events. Explicit announcements of a second reset remain separate.
Regular and banked events are distinct. The main reset count and completed-gap samples use regular events only; banked credits are counted separately. During editorial review, automatically grouped needs_review events remain in statistics with a visible review notice.
A small memoryless estimate
The model uses the latest eight completed gaps between regular events. The ongoing wait is excluded. Let the sample mean be μ days and λ = 1 / μ per day. The estimated chance of a reset in the next 24 hours is 1 − exp(−λ); for 48 hours it is 1 − exp(−2λ).
This assumes a stable independent cadence. Under this memoryless assumption, waiting longer does not increase the probability. It is neither an official promise nor a calibrated guarantee about future announcements.
When the estimate is hidden
A same-day confirmed reset takes priority. A timed official preannouncement takes priority over the probability. With fewer than five completed gaps, or when the ongoing wait exceeds three times the sample mean, the page withholds probabilities.
Sample variation determines the confidence label: medium only for a coefficient of variation below 0.5, otherwise low. The tracker never labels this estimate high confidence.
Read the distribution as history
The homepage shows the median completed gap from the last 30 days and the longest completed wait. The history page includes the all-time mean and full timeline. Hourly charts show when past events were recorded in UTC, your local zone, or Pacific time. They are not a timetable.
Alerts follow confirmation
Enabled email, Telegram and team-webhook alerts trigger after completion is confirmed. An official scheduled time can appear as a countdown, but preannouncements do not trigger email. Collection and delivery can be delayed; follow the original source and check your own Usage display.
Method reviewed on 2026-10-29. Account guidance: OpenAI pricing.