Is this your situation?
- You saw a reset claim on social media and want to know whether it was an announcement, a completed action, or speculation.
- Your limit banner still appears after someone else says their usage recovered, and you need to check whether the stated plan or account scope includes you.
- You are comparing a UTC-dated post with a local calendar date and might be looking at two different days.
- The source feed is unavailable or late; you need a reliable next check instead of a false “no reset” answer.
Step by step
- Read the source status first
The module above shows whether the transcript feed has been refreshed recently. If it says unavailable, open the linked X account directly. Do not infer that no post exists from an unavailable feed. The module never reads your ChatGPT account.
- Separate reviewed events from candidates
A reviewed event has a recorded source link and editorial check. Candidate posts are text imported from a third-party tracker and may be incomplete or wrong. “Reset announced” on a candidate is a wording classification, not a confirmation that the post is authentic or that OpenAI applied a reset.
- Check the date and scope
The headline state uses a UTC calendar day. The adjacent result covers the previous 24 hours, while your browser shows local time. Read the plan, region, workspace, and effective-time wording in the original source. OpenAI says one-time resets can have different eligibility and covered limits.
- Check your own allowance
Open Settings → Usage or the Codex usage page in your account. Compare the exhausted window, the displayed reset time, and any available reset count. A public automatic reset is not saved for later; a banked reset is stored until you apply it. Neither a post nor this page can see whether your account changed.
- Escalate an actual mismatch
If your usage appears wrong, a reset you were eligible for was not applied, or access has not returned after the stated account reset time, contact OpenAI Support with the account, timestamp, and source. OpenAI states that Support investigates these cases but does not manually grant a reset on request.
Still stuck?
- Check the official Codex service status as a separate question; an outage and a usage reset are different events.
- If the feed is stale, wait for a fresh check or open the source account yourself. Do not treat an empty candidate list as a final answer.
- If the personal timer you saved here reaches zero but your account still shows a limit, follow the reset-time-passed guide rather than repeating the timer.
Frequently asked questions
Does a “reset announced” candidate mean my Codex account reset today?
No. It describes wording in a third-party transcript. Check the original post, eligibility, effective time, and your own Usage screen before drawing a conclusion about your account.
Why can this page say today while it is already tomorrow for me?
The headline event window is the UTC calendar day. Your browser also displays local time and a rolling past-24-hour view so a time-zone boundary is visible.
Can this page prove that no Codex reset happened?
No. A stale feed or an empty reviewed-event list cannot prove absence. Even a complete public announcement record would not reveal the state of your private account.
Sources and scope
The sources below support the product behavior described here. Any live transcript classification is our interpretation, not a reading of your OpenAI account.
- Using Codex with your ChatGPT plan ↗ — One-time reset eligibility, automatic versus banked resets, account usage view, and support route.