Skip to content

Codex keeps running after weekly limit is reached, without consuming remaining credits #18018

Closed
Closed
Codex keeps running after weekly limit is reached, without consuming remaining credits#18018
Labels
bugSomething isn't workingrate-limitsIssues related to rate limits, quotas, and token usage reporting

Description

@rafaself
rafaself
opened on Apr 15, 2026

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.

Image Image

What steps can reproduce the bug?

  1. Use Codex until the weekly limit reaches 0% remaining.
  2. Start a new thread after the weekly limit has been exhausted.
  3. 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.

Activity

  1. rafaself
    added
    bugSomething isn't working
    on Apr 15, 2026
  2. github-actions
    added
    codex-webIssues related to Codex Web
    rate-limitsIssues related to rate limits, quotas, and token usage reporting
    on Apr 15, 2026

  3. github-actions commented on Apr 15, 2026

    @github-actions
    github-actionsBot
    on Apr 15, 2026 – with GitHub Actions
    Contributor

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

    Powered by Codex Action

  4. etraut-openai
    removed
    codex-webIssues related to Codex Web
    on Apr 15, 2026

  5. namevinu commented on Apr 18, 2026

    @namevinu
    namevinu
    on Apr 18, 2026

    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

  6. brunolemos commented on May 15, 2026

    @brunolemos
    brunolemos
    on May 15, 2026

    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.

    Image

    Source:

  7. rafaself commented on May 16, 2026

    @rafaself
    rafaself
    on May 16, 2026
    Author

    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.
    Image

    Source:

    * https://x.com/sama/status/2049492646792757552
  <img alt="Image" width="556" height="399" src="https://private-user-images.githubusercontent.com/619186/593379482-d7c2c28c-83c9-48dd-ab79-3a6c541c0d1b.png?jwt=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3Nzg4OTQ0MTgsIm5iZiI6MTc3ODg5NDExOCwicGF0aCI6Ii82MTkxODYvNTkzMzc5NDgyLWQ3YzJjMjhjLTgzYzktNDhkZC1hYjc5LTNhNmM1NDFjMGQxYi5wbmc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjYwNTE2JTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI2MDUxNlQwMTE1MThaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT1hZDBmZGI5MTc1YmE5M2U4YWU3ZDU3MDViODAxNGYxNjU0ZTViOGQ3NjEyOTg0NzA0M2NmZGExOTBhNmY1ZmE1JlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCZyZXNwb25zZS1jb250ZW50LXR5cGU9aW1hZ2UlMkZwbmcifQ.jH38Jp62ww_7-o-PCzNLVWEDZ3SsHCxFvEJ6vuh9Hi8">

* https://x.com/thsottiaux/status/2049498939641217287?s=20
  <img alt="Image" width="555" height="906" src="https://private-user-images.githubusercontent.com/619186/593379310-c07a5752-2d8f-466e-9bab-36b7475608ee.png?jwt=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3Nzg4OTQ0MTgsIm5iZiI6MTc3ODg5NDExOCwicGF0aCI6Ii82MTkxODYvNTkzMzc5MzEwLWMwN2E1NzUyLTJkOGYtNDY2ZS05YmFiLTM2Yjc0NzU2MDhlZS5wbmc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjYwNTE2JTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI2MDUxNlQwMTE1MThaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT01MzU2NjRmMzVlMDhiNzIwMTdiYmVkYzE4YWI0ZDYwYWI4NGViNWEyMTQ5MDVlZWMxNTI2NjFiYzc0ZDBiZWViJlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCZyZXNwb25zZS1jb250ZW50LXR5cGU9aW1hZ2UlMkZwbmcifQ.vpe0_Nu1tJwf4ImGyA8dpz_EAFQarKtjIf_fKd1a8fg">

    This is great, but it was not exactly the situation in the issue. Also, it seems to be fixed already.

  8. rafaself commented on May 16, 2026

    @rafaself
    rafaself
    on May 16, 2026
    Author

    This issue seems to be already solved since it is not happening anymore.

  9. rafaself
    closed this as completedon May 16, 2026

  10. siahisaforker commented on May 28, 2026

    @siahisaforker
    siahisaforker
    on May 28, 2026

    they patched this. it immediately stops now. kinda ruined it

  11. thisistuhinsen commented on May 30, 2026

    @thisistuhinsen
    thisistuhinsen
    on May 30, 2026

    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.

  12. namevinu commented on Jun 1, 2026

    @namevinu
    namevinu
    on Jun 1, 2026

    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.

  13. siahisaforker commented on Jun 1, 2026

    @siahisaforker
    siahisaforker
    on Jun 1, 2026

    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

  14. thisistuhinsen commented on Jun 1, 2026

    @thisistuhinsen
    thisistuhinsen
    on Jun 1, 2026

    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.

  15. Lucid-IDE commented on Jun 3, 2026

    @Lucid-IDE
    Lucid-IDE
    on Jun 3, 2026

    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.

  16. TheRabbitHoleDev commented on Jun 8, 2026

    @TheRabbitHoleDev
    TheRabbitHoleDev
    on Jun 8, 2026

    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

    Image Image

  17. li01223123 commented on Jun 13, 2026

    @li01223123
    li01223123
    on Jun 13, 2026

    it's over

  18. kudasaixc commented on Jul 12, 2026

    @kudasaixc
    kudasaixc
    on Jul 12, 2026

    Keeps working exactly like that for me.

  19. DrescoAV commented on Jul 12, 2026

    @DrescoAV
    DrescoAV
    on Jul 12, 2026

    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?

  20. bennypea commented on Aug 17, 2026

    @bennypea
    bennypea
    on Aug 17, 2026

    Snitch

  21. DrescoAV commented on Aug 17, 2026

    @DrescoAV
    DrescoAV
    on Aug 17, 2026

    Snitch

    At that time OpenAI openly shared that's how it worked. Not its not anymore

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't workingrate-limitsIssues related to rate limits, quotas, and token usage reporting

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions