Codex Reset
An announcement can tell you that a reset was reported. Your account’s Usage screen tells you which limits and refresh times apply to you. Here is how to read both without confusing them.
This tracker follows public announcements. It does not connect to your account, calculate your remaining allowance or know your next personal refresh time. A recent announcement is not evidence that your own limits changed.
Check Usage in Codex for your current allowance and next refresh. Make sure you are looking at the correct account, workspace and usage limit. Your subscription billing date and a usage refresh are different things.
An automatic reset applies directly to the accounts and allowances covered by an offer. A banked reset is saved for later use. Receiving a banked reset does not itself replenish your allowance.
Check eligibility and any redemption deadline in the original announcement and your account. Even a reset described as global need not cover every account or every limit. Historical averages do not promise another offer.
A scheduled reset records an announced future window. Passing that time alone does not confirm completion. Reset watch is a forecast based on signals, not an official promise.
Completed records, schedules and forecasts are displayed separately. A short post such as “Done” does not establish which plans were included; the original thread may supply context, otherwise the scope remains unspecified.
Choose your display time zone or use your browser’s local time. Language does not determine time zone. UTC is available as a common reference, and the history calendar groups records by UTC date.
The publication time tells you when an announcement was posted or an event was recorded. It is not automatically the time a reset took effect. A date can fall on the next or previous day after time-zone conversion.
Records come from the public Codex Resets feed. Local summaries explain the record; original wording and source links remain available. If the source does not state an audience or effective time, the tracker does not fill it in.
For an apparent discrepancy, open the original source and its surrounding discussion. Updated source records and summaries may change. Neither a summary nor a browser alert independently verifies a reset on your account.
We organize public records from Codex Resets. Summaries do not confirm changes to your account and may be revised when the source changes. Follow the original source for context and corrections.
Full history →