Skip to content

Quotas draining like crazy: burnt 100% of my 5h limit in 10 min on Business #20153

Open

Description

@fohoizey2

What version of the Codex App are you using (From “About Codex” dialog)?

v0.125.0

What subscription do you have?

Business

What platform is your computer?

macOS

What issue are you seeing?

Hi,
I've been using Codex since day one, but I now feel very disappointed.
I burned through my 5-hour quota in less than 10 minutes this morning using 5.5 High in plan mode and 5.5 Low for implementation.
About a month ago, it felt almost unlimited, but now I’m getting a Claude-like experience!
Is there a bug causing this?
Thanks

What steps can reproduce the bug?

Just use Codex

What is the expected behavior?

No response

Additional information

No response

Activity

  1. added
    appIssues related to the Codex desktop app
    on Apr 29, 2026
  2. added
    bugSomething isn't working
    rate-limitsIssues related to rate limits, quotas, and token usage reporting
    on Apr 29, 2026
  3. removed
    appIssues related to the Codex desktop app
    on Apr 29, 2026
  4. mnj commented on Apr 29, 2026

    @mnj

    Yep, had to switch back to 5.4, which is working as expected with much lower drain on credits, if the usage limits for 5.5 is working as intended, then it's barely useable at all on a business plan, for anything but two simple prompts for minor code changes every 5h.

    But "luckily" 5.4 is pretty decent even compared to 5.5 for the tasks we use it for here at work, didn't notice any real code quality benefit with 5.5 for our codebase over 5.4

  5. daletman commented on Apr 29, 2026

    @daletman

    Had exactly the same experience today. One prompt with 5.5 xHigh running for 10-20 minutes and quota was 0. That's just useless.

  6. indyavik commented on May 27, 2026

    @indyavik

    I am seeing this too. specially on 5.4 quota is disappearing very fast

  7. t-var-s commented on Sep 1, 2026

    @t-var-s

    I’m seeing what appears to be the same issue on a ChatGPT Business seat, and I have a fairly clear reproduction from today (Sep 1).

    In a single existing thread:

    • Model: GPT-5.6 Sol
    • Reasoning: High
    • Fast mode: Off
    • Interaction: One new prompt, asking Codex to make me a plan
    • Elapsed time: 10 minutes 27 seconds
    • 5-hour quota: 93% remaining → 9% remaining

    So one prompt consumed 84 percentage points of the 5-hour quota in about 10.5 minutes.

    This has not been a one-off for me. I’ve seen repeated cases with different projects where a single thread/new prompt consumes roughly 80% of the 5-hour allowance within around 10 minutes.

    I understand that High reasoning and a large existing context can consume more tokens, but this level of depletion seems disproportionate, especially with Fast mode disabled and only one foreground request.

    This looks very similar to the original report in this issue, except I’m now reproducing it with GPT-5.6 Sol.

  8. t-var-s commented on Sep 2, 2026

    @t-var-s

    I have a fairly clear reproduction from today (Sep 1)

    Sent feedback ID 01a05e14-a9d5-7962-a1b4-6eb9d3cfb643 for this specific thread.

    The full 5h usage window started by resuming a previous thread that was interrupted while 5.6 Sol High tried to debug why these usage spikes keep happening. Context window was more than half full, so I called /compact and the 5h usage went from 100% to 94% before I asked the agent to resume its work (which you have to do now since threads get interrupted when usage hits 0).

    Agent responds, some change to AGENTS.md is suggested, 5h usage goes to 93%. I close the ChatGPT desktop app (version 26.825.51511 on Intel MacOS 15.7.7) and open it again to make sure the change gets applied. Start a new thread and ask for a plan. That's when usage goes from 93% to 9% in ten minutes.

    In summary:
    resume previous thread with a /compact - 94%
    ask to finish work that was interrupted by the 5h limit - 93%
    restart app, new thread, prompt for a plan - 9%

    I have similar cases to this from the previous week and the week before.

    Edit: Following morning (Sep 2), new thread, implement that plan, usage gone again already.

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