Codex keeps running after weekly limit is reached, without consuming remaining credits
What issue are you seeing?
I reached my weekly Codex limit, but Codex continues to run. The weekly quota is exhausted, and although I still have credits available, they are not being used. This seems inconsistent with the expected billing or usage behavior.
<img width="582" height="213" alt="Image" src="https://github.com/user-attachments/assets/b675290b-a0fa-4ba3-b64b-cd3dd285b1dc" />
<img width="1262" height="428" alt="Image" src="https://github.com/user-attachments/assets/b6367d8e-fed0-427e-9aba-23495aca6942" />
What steps can reproduce the bug?
- Use Codex until the weekly limit reaches 0% remaining.
- Start a new thread after the weekly limit has been exhausted.
- Observe that Codex still runs instead of stopping or consuming the remaining credits.
What is the expected behavior?
Once the weekly limit has been reached, Codex should clearly notify the user that the weekly quota has been exhausted and indicate when it will reset. If credits are still available, Codex should continue running and consume those credits as documented. Otherwise, it should stop running tasks.
Additional information
- I initially thought this might be related to a credit booster I apparently received, but I am not sure whether that is affecting the behavior.
- Although it keeps running, it is apparently slower than before, because it is taking too much time in thinking in basic tasks.
15 Comments
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
Same thing happened to me. My 5 hour weekly limit are exhausted mid task but still it kept going without stopping. It would be worthwhile to check if the model is being degraded when the limits are exhausted instead of hard stopping the task (like what happens in the claude code and antigravity)? Or is this a genuinely a bug?
I was using gpt 5.4 with reasoning = high
This is by design. OpenAI did this to provide a better user experience (at the expense of their profit margin), preventing the tasks from getting aborted midway. No extra charge happens. Consider this a curtesy from OpenAI and use it with good faith (don't abuse too much).
If will eventually stop though, e.g. if you try to send another message or it tries to compact the context.
<img width="825" height="112" alt="Image" src="https://github.com/user-attachments/assets/eb5663df-48da-4285-be3d-4a3c2341b3b4" />
Source:
<img width="556" height="399" alt="Image" src="https://github.com/user-attachments/assets/d7c2c28c-83c9-48dd-ab79-3a6c541c0d1b" />
<img width="555" height="906" alt="Image" src="https://github.com/user-attachments/assets/c07a5752-2d8f-466e-9bab-36b7475608ee" />
This is great, but it was not exactly the situation in the issue. Also, it seems to be fixed already.
This issue seems to be already solved since it is not happening anymore.
they patched this. it immediately stops now. kinda ruined it
They were at first thinking as a Product where the User experience mattered but now I guess they don't. If a task is running, and your daily limit has expired but your weekly limit is left, I think the ideal path should be to let the task finish and deduct from the weekly limit for that particular task to finish at least. This should be allowed for the users to pursue a goal or finish a task gracefully. If you are designing for user experience, then this is the bare minimum.
No, it keeps working. I guess I am lucky that I have not received that update yet, but given the codex ample limits in $20 plan compared to claude code, cant complain even if it stops immediately after limits are exhausted.
When i posted it, it was when they made the stricter limit following for free tier. They accidentally applied it to all paid plans. Has since been resolved, I dont have any other issues
I have noticed that it continues for a while until it stops in the free when the task is ongoing and go tier but immediately stops in a prolite plan. But yes, I agree compared to claude it does give more limits which is more practical in my experience.
Been running 5 agents gpt 5.5 xhigh fast mode working on massive project of millions of lines of code. One agent is itself managing a swarm of agents and has called over 600 agents in 24 hours. I hit usage limits for the week yesterday morning and the current weekly usage bar is not even showing anymore above the 5h that is stuck at 100%. Im on pro 5x and downgraded to plus and currently cli says im on plus. Even when red warning saying ive hit limit appears, the agents continue working even when re prompted.
I wont complain, I do have 0 credit for more usage. For the first time I really started to work with "Goals" and when the weekly limit arrive, i got a popup to "add credits" but it is now still working for the last hour and I wont stop it overnight hoping that it just continues :D
<img width="196" height="67" alt="Image" src="https://github.com/user-attachments/assets/0884b99f-15f6-4240-9f16-cacc589075f1" />
<img width="935" height="355" alt="Image" src="https://github.com/user-attachments/assets/33a7b0b0-a100-4b4d-ae13-9297d530f55b" />
it's over
Keeps working exactly like that for me.
which version of codex are you using? desktopp app, extension or cli? and on what OS? what type of account?