Skip to content

Codex blocked after quota was consumed during inactivity #28694

Open

Description

@excessive-eng

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

Version 26.611.61753

What subscription do you have?

MacOS

What platform is your computer?

No response

What issue are you seeing?

  • Max subscriber.
  • One user request.
  • Session idle.
  • Quota continued decreasing.
  • Codex became unavailable.
  • Existing report: Limits despair #28687.

What steps can reproduce the bug?

  1. Open Codex in the ChatGPT macOS application.
  2. Open an existing Codex session.
  3. Do not submit any new prompts.
  4. Do not start any new tasks, code reviews, repository indexing operations, or agent executions.
  5. Leave the session open and monitor quota usage.
  6. Observe that:
    • The session ID remains unchanged.
    • Context size remains unchanged (139,441 / 258K).
    • No visible tasks are running.
    • Local CPU utilization remains near zero for most of the observation period.
  7. Despite the absence of user activity, both the 5-hour and 7-day quotas continue to decrease.
  8. Continue observing until the 5-hour quota is exhausted and Codex becomes unavailable.

Observed example:

09:52
5-hour quota: 67%
7-day quota: 95%

10:04
5-hour quota: 58%
7-day quota: 93%

10:21
5-hour quota: 47%
7-day quota: 92%

10:27
5-hour quota: 43%
7-day quota: 91%

11:06
5-hour quota: 16%
7-day quota: 87%

Eventually the 5-hour quota reached zero and Codex access was blocked despite only one user prompt being submitted during the observation period.

What is the expected behavior?

No response

Additional information

No response

Activity

  1. added
    bugSomething isn't working
    rate-limitsIssues related to rate limits, quotas, and token usage reporting
    on Jun 17, 2026
  2. github-actions commented on Jun 17, 2026

    @github-actions
    Contributor

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

    Powered by Codex Action

  3. excessive-eng commented on Jun 17, 2026

    @excessive-eng
    Author

    I reviewed issue #28085.

    While there are similarities regarding unexpected quota consumption, my issue appears to be different.

    In my case:

    • The quota depletion was observed in real time.
    • A single Codex session remained open.
    • Session ID remained unchanged.
    • Context size remained unchanged.
    • No prompts were submitted.
    • No visible tasks were running.
    • CPU monitoring was performed on the ChatGPT macOS application.
    • Quota continued decreasing during the observation period.
    • The 5-hour quota was eventually exhausted, resulting in loss of access to Codex.

    The issue is not only unexplained historical usage in analytics, but active quota depletion during an apparently idle session.

    Therefore I believe this issue should remain open unless the engineering team confirms it is the same underlying root cause.

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

    appIssues related to the Codex desktop appbugSomething 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