NEXTRESET / ABOUT
Sources & methodology
How NextReset collects, classifies, and displays public Codex reset announcements.
A clear record, with its sources.
NextReset is an independent tracker for people who want to know whether an additional Codex reset has been announced. We publish concise summaries with source links, rather than asking for access to your account.
Where the records come from
We currently synchronize with a public announcement archive API, a third-party archive that tracks Tibo (@thsottiaux). We are not currently connected directly to the X API. Every available original post is linked. Source records marked “observed” retain that label; their timestamp may describe an archive observation rather than a post’s publication.
Freshness and failure handling
A Cloudflare scheduled job checks the archive every 15 minutes. We validate the data and save a complete snapshot. If a sync fails, the previous snapshot remains available. After 45 minutes without a successful check, the page displays a delayed-sync label. A successful API check confirms retrieval; it does not guarantee that the upstream archive has seen every new post.
Last successful sync:
Classification and corrections
We separate regular usage resets, banked credits, combined announcements, and targeted compensation. Editorial summaries can clarify a source classification. An observation is not independent verification. A pending announcement stays pending even after its estimated time passes. We do not turn AI watch probabilities into a promised reset time.
How the numbers are calculated
The total counts announcement records, not the number of credits or affected accounts. Average and longest gaps use adjacent record times across the full archive, including saved-credit and compensation entries. The calendar shows the current UTC week and the previous 25 weeks. All of these describe the past, not an expected future schedule.