Your Codex reset time passed but you still have no access

First, the honest framing

A reset time passing is not a promise that everything will be fine. It is the point at which you are entitled to expect access and, if it has not returned, to ask why.

This is exactly the case the official guidance addresses: contact support when access has not returned after the stated reset time. That is a support case, not a client-side bug you can fix by deleting a directory.

Checks to run first, because they change what you are asking about

Do these before you write to anyone. Each one, if it applies, means you are not actually in the “reset passed and nothing happened” case at all.

1. Which allowance were you reading? There may be more than one on your account. A reset of one does not necessarily clear another.
2. Is this plan-based usage or API-key billing? These are separate arrangements with separate allowances. A reset on one does nothing for the other.
3. Are you in a workspace? On token-based workspace arrangements, an administrator controls the effective user limit and the reset period. Your access can be governed by a policy you cannot see.
4. Did you recently apply a banked reset, change plan, or receive a grant? Any of these can move your weekly reset date. Read the usage screen again rather than trusting a note you made earlier.
5. Did you enter the time in the right timezone? This is the single most common self-inflicted version of this problem. The reset time in your account is a specific instant; if you converted it to a local time by hand, re-check the conversion. If you are using this site’s personal timer, the timer shows you both your local time and UTC precisely so that this mistake is visible.
6. Has enough time actually elapsed? Compare against the exact instant, not against a rough sense of “it should be done by now”.

What to do when none of the above applies

Contact support. When you do, include:

• the plan or workspace type,
• the allowance you believe was exhausted,
• the reset time your account displayed, including the timezone you read it in,
• when you last successfully made a request,
• what you see now, quoted rather than summarised.

The official guidance covers three specific support-worthy cases: usage that appears incorrect, access that has not returned after the stated reset time, and a reset you were eligible for that was not applied as described.

What not to do

• Do not ask support to reset your limits. The official guidance states plainly that support does not reset ChatGPT or Codex usage limits. That request will be declined, and it obscures the real case you are reporting.
• Do not reinstall the client. Account state is not stored in your installation. Reinstalling costs you time and changes nothing about the allowance.
• Do not delete your configuration. Same reason, plus you lose your setup.
• Do not assume a further reset is coming. Nothing in the documented material says a passed reset time triggers a new one, or that an automatic reset is banked for later — the official description is that an automatic reset is applied directly and is not saved.

How to tell it is resolved

Requests are accepted, and the usage screen shows an allowance that is no longer exhausted. If you applied a banked reset to get there, note the new weekly reset date.

Known limits of this guidance

• Evidence level: documentary. The official article addresses this case briefly; this guide does not extend beyond what it says.
• No client-side remedy is offered because none is documented. Any instruction you see elsewhere to reinstall, clear caches or edit configuration in response to this specific case is not supported by the sources checked here.
• Support response times and channels are outside the scope of this guide.