Skip to content

Codex CLI consumed top-up credits and depleted 5-hour limit unexpectedly after latest update #15959

Closed as duplicate

Description

@Kokoabassplayer

What version of Codex CLI is running?

codex-cli 0.117.0

What subscription do you have?

plus plan 20$

Which model were you using?

5.4-codex xhigh

What platform is your computer?

Microsoft Windows NT 10.0.26100.0 x64

What terminal emulator and version are you using (if applicable)?

powershell

What issue are you seeing?

After updating Codex CLI today, usage and billing behavior changed unexpectedly. While I still had weekly quota available, Codex CLI consumed my top-up credits down to zero, and my 5-hour limit was also depleted. In my case, the 5-hour limit does not appear to be applied correctly when using paid credits. This behavior did not happen before the update, so I believe it may be a bug.

What steps can reproduce the bug?

Uploaded thread: 019d2936-62c7-70e0-8816-b23255a12f69

What is the expected behavior?

The expected behavior is that Codex CLI should apply weekly quota, top-up credits, and the 5-hour limit correctly and consistently.

In my expected flow, when weekly quota is still available, usage should follow that quota as intended. When weekly quota is exhausted, I should still be able to continue working by using my purchased top-up credits. If paid credits are being used, the system should not unexpectedly deplete both my credits and the 5-hour limit in a way that was not happening before.

I also expect billing and usage behavior to remain consistent across versions unless there has been a clearly documented change.

Additional information

Additional context:

  • This issue started only after I updated Codex CLI to the latest version today.
  • Before this update, my understanding and experience were that when my weekly quota was exhausted, I could continue working by using purchased top-up credits.
  • After updating, Codex CLI appears to have consumed my paid credits even though I still had weekly quota available, and my 5-hour limit was also depleted.
  • Because of this change in behavior, I suspect there may be a regression or billing/usage-tracking bug in the latest version.
  • This directly affected my workflow, because I purchased credits specifically to continue working after my weekly quota runs out, not to have both usage pools impacted unexpectedly.

If needed, I can also provide:

  • the Codex CLI version I updated to
  • the approximate time the issue happened
  • screenshots of my quota/credit usage before and after
  • any relevant logs or terminal output

I would also like to request a review of the credits that were consumed during this issue. Since this behavior appears to be unintended and only started after the latest update, I believe the affected credits should be restored if the team confirms this was a bug or incorrect billing behavior.

Activity

  1. added
    CLIIssues related to the Codex CLI
    windows-osIssues related to Codex on Windows systems
    rate-limitsIssues related to rate limits, quotas, and token usage reporting
    on Mar 27, 2026
  2. removed
    windows-osIssues related to Codex on Windows systems
    CLIIssues related to the Codex CLI
    on Mar 27, 2026
  3. etraut-openai commented on Mar 27, 2026

    @etraut-openai
    Contributor

    Usage accounting is not under control of the client, so any behavioral changes you may have seen are not related to the client update.

    I suspect what happened is that you depleted your 5-hour usage, and credits were applied once that was exhausted, allowing you to continue to work.

  4. Kokoabassplayer commented on Mar 30, 2026

    @Kokoabassplayer
    Author

    I suspect the 5-hour limit is being depleted much faster than before. For example, it took only a single rebase on one PR to push me close to the limit. Previously, I was able to work through many more issues and merge significantly more PRs within the same allowance, but that no longer seems to be the case.

    At minimum, I need the tool to remain usable for real work and actual delivery, because it is highly disruptive when the limit is reached in the middle of a task. At the current rate of depletion, and with no mid-tier plan available between the $20 and $200 options, while credit top-ups are also very expensive, I do not have many practical choices here.

    Thank you for your attention

  5. etraut-openai commented on Mar 30, 2026

    @etraut-openai
    Contributor

    We're tracking this issue in #14593.

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