Codex dekstop limits bug
Open 💬 6 comments Opened Jun 15, 2026 by Flaain
💡 Likely answer: A maintainer (github-actions[bot], contributor)
responded on this thread — see the highlighted reply below.
What version of the Codex App are you using (From “About Codex” dialog)?
26.609.41114
What subscription do you have?
Plus
What platform is your computer?
x64
What issue are you seeing?
Limits back to previous before reset
What steps can reproduce the bug?
After migrating from the CLI to the Desktop app, Codex gave me the opportunity to reset my usage limits. I reset them and continued working. However, after hitting my 5-hour limit window, my weekly limits returned to the previous usage before the reset. Therefore, I am now seeing that my weekly limits will be reset on June 18th, rather than June 22nd.
Maybe it's not about desktop app because im checking limits in web.
What is the expected behavior?
Keep new limits
Additional information
_feedback ID - 019eca74-7282-7ae3-9daf-c08128ee35f8_
6 Comments
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
The same issue also in my case: no-active-thread-019eccdb-3a7f-7230-ab03-5a786a23ec5c
Mine still says 0% weekly even after a reset, but interestingly some chats still can work while others don't. 019ed512-4eda-7ee2-8693-d5827210bc9e
Same issue. Spent 2 resets, non of them worked.
I had 0% usage remaining in 5h window and 32% in weekly window. Codex offered to use reset (I had 3 of them). I did. The count of resets I have became 2, but usage remaining didn't change. Still 0% in 5h and 32% in weekly.
Tried to restart Codex app, logout/login, to check my remaining usage in CLI instead of app. Nothing helped.
Then I tried second time. Spent one more reset. The result was the same.
Please fix that bug AND give me my 2 resets back. Account – egrik213179@gmail.com
Same thing. Spent 2 resets that did not work. OpenAI Support says there is nothing they can do - and that banked resets can not be reissued.
Please fix and restore my resets! Case Number: 11209586
~Same 019fbacc-db0c-7fe1-82c2-39040333df28~ eventually fixed itself after 20 minutes.