About codexreset.live

What we track

We organize public announcements and source-linked signals about Codex usage resets, including scope, type, and review state. Personal 5-hour and weekly limits remain account-specific; they are not silently converted into public events.

Our review method

The workflow is: a monitoring signal surfaces a candidate; we inspect the original public source; we record its scope, type, state, author, and timestamps; then a person checks the entry before it is published. A source can support an announcement without proving that rollout finished.

Source hierarchy

We prefer the original public announcement or status source, then a directly attributable public report. Search snippets, copied summaries, and an individual account screenshot are discovery clues, not equivalent evidence. Each archive row links to the source used for review.

History versus live status

The history page is a static, manually reviewed archive with a stated review time. The home page's live status is a current classification of available public signals. Neither is a private-account monitor, an official OpenAI database, or a promise of the next reset.

What we cannot access

We cannot read your Codex account, plan, usage window, private reset time, or private dashboard. For your own allowance, check the official usage dashboard or run /status in the Codex CLI. For plan context, see the official OpenAI pricing documentation.

Corrections and independence

codexreset.live is not affiliated with, endorsed by, or operated by OpenAI. If an archive row has a wrong source, scope, type, or state, report the original URL and proposed correction through the public GitHub issue tracker. We review the evidence before changing the record.