Collection and checks
On a schedule, we collect posts and replies from OpenAI accounts on X, keeping each post's link and timestamp. Codex resets used to be posted by Tibo; since November 3, 2026, Andrew Ambrosino posts them. We also read the public Codex reset history, and we use our own test account to check when usage resets and banked resets actually land. Every statement names its source.
Home page status
- If OpenAI has posted an announcement on X since the last reset, it shows the announced timing (e.g. "Next week") and when the last reset happened;
- If a reset happened in the last 24 hours, it shows "Reset", the reset time and the original post;
- Otherwise, it shows how many days it's been since the last reset;
- If data updates are delayed, it shows when the data was last updated.
Estimates from history
When nothing has been announced and the data is fresh, the page shows an experimental estimate for the next 24 hours and 3 days. The baseline is the reset rate of the last 15 days, treating a reset as equally likely at any moment, whatever the time since the last one. A limited hint in an OpenAI post can add an adjustment that fades over time, either up (a reset soon) or down (what comes next looks more like an improvement than a reset). Only one hint counts at a time. A hint its author says was resolved in a later reply stops counting, and any other expires after 48 hours or when a new event arrives. There are few resets in the last 15 days, so the estimate changes noticeably with each new reset. While Tibo's 28-day challenge ("an improvement or a reset every day") runs, the usual rate stays fixed at that of the 15 days before the challenge began, and the extra daily chance the challenge brings is added on top (whether the next day is a reset day depends on the day before, so the share of reset days following a reset day and following an improvement day is learned separately from the days logged so far). With no hint in play, the odds during the challenge are therefore higher than usual. This is a statistical estimate from past data, not an official forecast.
Who gets it, and when it lands
When an announcement names which users are included, the page shows those plans. Our test account confirms when a usage reset or banked reset lands, and that time is shown on the Codex page.
Publishing
Collected and processed JSON goes to this site's data domain. The home and Codex pages reload it every minute; RSS, the calendar, history and event pages update when the static site is rebuilt.