THE TIMING
When does Codex reset?
Your own usage window and a public reset announcement are two different clocks.
Start with your own clock
Open the usage dashboard for the account and workspace you actually use. Its displayed reset time is the relevant reference for your personal allowance. In an active CLI session, /status can show your remaining limits.
Treat extra resets as announcements
NextReset follows public reset reports. A recent announcement does not establish a recurring appointment: an incident, launch, or milestone can explain one event without predicting the next. Our elapsed timer measures time since a historical report; it is not counting down to free usage.
Read the two times carefully
The archive stores announcement or observation times in UTC. You can switch the displayed times to your local zone. A message published around midnight can fall on different calendar dates in different countries. The calendar deliberately stays in UTC so that the same report always belongs to the same square.
A practical way to use the tracker
Check your own dashboard first, then look at the latest broad reset and latest update separately. Open the original source when the scope matters. If the source sync is delayed, treat the saved archive as historical information. If a future reset is announced, we keep it separate from recorded resets until the source reports execution.