›_ Codex Issues
Codex Issues / #31532

Codex reset was consumed but usage limit was not reset

Open 💬 7 comments Opened Jul 8, 2026 by weihao-ma
💡 Likely answer: A maintainer (github-actions[bot], contributor) responded on this thread — see the highlighted reply below.

What version of the IDE extension are you using?

26.623.141536

What subscription do you have?

Plus

Which IDE are you using?

VS Code

What platform is your computer?

_No response_

What issue are you seeing?

I used one available Codex reset, but my Codex usage limit was not actually reset.

The reset count was deducted successfully, so the reset appears to have been consumed. However, my usage/limit status remained unchanged and I still could not use the restored quota as expected.

What steps can reproduce the bug?

Feedback ID: no-active-thread-019f409b-98bb-7083-8266-bbcd95aab948

What is the expected behavior?

The Codex usage limit should be reset after redeeming a reset.

Additional information

_No response_

View original on GitHub ↗

7 Comments

github-actions[bot] contributor · 12 days ago

Potential duplicates detected. Please review them and close your issue if it is a duplicate.

  • #31450
  • #30349

Powered by Codex Action

Ritotheven · 11 days ago

I’m seeing the same reset-consumed-without-persistent-reset behavior on Codex Desktop 26.623.19656 with ChatGPT Pro.

Repro:

  • A Codex reset credit was redeemed; the backend now reports availableCount=0.
  • Immediately after a normal account token refresh, account/rateLimits/read returned main Codex weekly usedPercent=0 (100% remaining).
  • A fresh app-server session 1-2 minutes later returned main Codex weekly usedPercent=99 (1% remaining), while the credit was still absent.
  • The browser usage page and ChatGPT/Codex app agree with the reverted 1% state.

This looks like a backend reconciliation/persistence issue rather than a UI cache issue. Feedback IDs: no-active-thread-019f4854-ef28-7f91-92f4-5568e4b29842, no-active-thread-019f4858-e64b-7df2-beb9-fb5bd5f53d9a, and no-active-thread-019f4862-f666-7e52-8a68-39b5b8f4efd0.

JshGrn · 11 days ago

+1 I just used the codex reset which has reset the cli I used it on, but not the other cli's or the usage web gui.

Zhaokix · 11 days ago

+1 used reset, but nothing happened still 0%

omniassist · 11 days ago

+1 Seems you, me and many others are also stuck with this - and my reset seems not to be for another 6 days so I cannot work
I hope Open AI will fix this soon. [https://github.com/openai/codex/issues/31450](url)

Other examples:
https://github.com/openai/codex/issues/31575
https://github.com/openai/codex/issues/31606

Zhaokix · 11 days ago
+1 Seems you, me and many others are also stuck with this - and my reset seems not to be for another 6 days so I cannot work I hope Open AI will fix this soon. [https://github.com/openai/codex/issues/31450](url) Other examples: https://github.com/openai/codex/issues/31575 https://github.com/openai/codex/issues/31606

I updated an app and limits come back to 100% in app and in the web. I updated app about 20 min ago

Support refused to help me, they insist that there is no problem and everything is working as usual. Deal with your problem yourself.

fbernklau · 10 days ago
> +1 Seems you, me and many others are also stuck with this - and my reset seems not to be for another 6 days so I cannot work > I hope Open AI will fix this soon. [https://github.com/openai/codex/issues/31450](url) > Other examples: > #31575 > #31606 I updated an app and limits come back to 100% in app and in the web. I updated app about 20 min ago Support refused to help me, they insist that there is no problem and everything is working as usual. Deal with your problem yourself.

But limits being back to 100 % is due to their issuing a global reset for everybody, not because they fixed whatever causes resets being consumed but not actually resetting the limits.