Client release v2.1.267Claude Code releases
Source ↗THE RESET OBSERVATORY
When will Claude reset?
Track Claude reset announcements, history, and experimental forecasts. Check Pro and Max coverage; regular renewals and limited compensation are separate.
Latest collected snapshot · 2026-09-10 10:31 UTC
CodexHistory availableClaudeHistory availableGeminiUsage rulesGLMReset cardsKimiReset recordsAntigravitySeparate quota
Loading collected public records…
Claude reset forecast
Target: a new Claude reset announcement for all users or a subscription tier. Check each announcement for plan coverage.
6.0%
Experimental probability of a new announcement within 24 hours of issue
Historical baseline 6.0%
- 24 hours
- 6.0%
- 48 hours
- 11.5%
- 7 days
- 34.2%
⚠ Incomplete or stale data; showing the previous forecastIssued Sep 10, 2026, 10:31 AM UTC
Event days in the forecast
5Historical observation span
90daysAvailable monitoring sources
0/ 3Forecast status
ExperimentalTHE RECORD
A source for every reset.
Client release v2.1.266Claude Code releases
Source ↗Client release v2.1.265Claude Code releases
Source ↗Client release v2.1.263Claude Code releases
Source ↗Public automatic reset · Max onlyClaude reset history
Source ↗Client release v2.1.261Claude Code releases
Source ↗Client release v2.1.260Claude Code releases
Source ↗Client release v2.1.259Claude Code releases
Source ↗FOLLOW THE SIGNAL
Public sources, clearly identified.
Codex and Claude use third-party reset catalogs. Other platforms show reviewed public records and official rules. Periodic rule checks do not discover new announcements. Regular renewals, manual reset cards and policy changes are kept separate from automatic-reset forecasts.
Claude reset history
StaleThird-party catalog · Official and team X announcements
Last success Sep 10, 2026, 10:31 AM UTC
Open source ↗Claude Status
StaleOfficial incident source
Last success Sep 10, 2026, 10:31 AM UTC
Open source ↗Claude Code releases
StaleOfficial GitHub · Not a model release
Last success Sep 10, 2026, 10:31 AM UTC
Open source ↗HOW WE ESTIMATE
An estimate,
not a promise.
Platforms can change their policies at any time. These estimates do not mean your account will receive a reset.
01Start with history, then consider new signals
Over the past 90 days, automatic reset announcements on the same UTC date count as one event day. We need at least 30 days of observation and 5 event days to show a probability. The third-party historical record may be incomplete.
The Gamma–Poisson model uses α = 1 + event days and β = 7 + observed days. The baseline probability of at least one announcement in the next h days is 1 − (β / (β + h))^α.
02How public signals affect the estimate
Reset previews, model releases, usage incidents, and community signals have manually chosen weights of 2.0, 0.35, 0.25, and 0.10. Each is scaled by source weight and decays with age. Only the past 72 hours count, and only the strongest signal in each group is used.
These weights are experimental assumptions, not trained or calibrated values. Banked resets and ordinary client updates do not increase the automatic-reset estimate. Without valid new signals, the adjusted estimate equals the baseline. The 7-day result is a longer-range extrapolation.
03How we evaluate forecasts
We save each forecast and its source cutoff times, then wait for the outcome. Missing collection periods do not count as “no reset.” We do not present another project’s results as our own.
Historical replay and prospective scoring are kept separate. We need timestamped forecasts and comparisons against the baseline using Brier score and Log Loss before claiming better accuracy.
04Open-source references and event definitions
tibo-reset-watch informed public-post monitoring; tibo-reset-lab provides an auditable forecasting experiment. This site is independently implemented.
Automatic resets, banked resets that must be redeemed, and regular account usage renewals are different events. Read OpenAI’s explanation ↗