Skip to content

Codex Pro 5x quota drops 2-3% for a single normal prompt, equivalent to 10-15% of Plus 5-hour quota #30909

Open

Description

@waitingformywind

Summary

I am on Codex Pro 5x. Recently, a single normal prompt can consume about 2-3% of my Pro 5x quota.

Since Pro 5x is 5x a Plus quota, this is equivalent to roughly 10-15% of a Plus 5-hour quota for one prompt. That implies a Plus user could only send about 6-10 normal prompts per 5-hour window, which seems clearly abnormal.

This does not look like normal high usage. It looks like a quota accounting / token burn issue.

Observed behavior

  • Plan: Codex Pro 5x
  • Date observed: 2026-07-02
  • A single normal prompt consumed approximately 2-3% of Pro 5x quota
  • Equivalent Plus 5-hour usage: approximately 10-15%
  • At that rate, one Plus 5-hour quota would only support about 6-10 normal prompts

Expected behavior

A single normal prompt should not consume 2-3% of a Pro 5x quota.

Even if the prompt has some context, the effective cost should not make a Plus-equivalent 5-hour quota disappear after only a few ordinary prompts.

Possible related areas to investigate

Please check:

  • server-side quota accounting / rate_limits.used_percent
  • repeated context billing
  • background agents or unfinished worker sessions
  • ambient suggestions / background summaries
  • subagent or forked thread sessions
  • usage meter display vs actual server-side metering
  • long-thread compaction or replay causing excessive billing

Related public reports

This appears similar to recent reports in this repository:

Impact

This makes Codex very difficult to use reliably, because even short conversations can consume a large fraction of the quota.

Activity

  1. added
    bugSomething isn't working
    rate-limitsIssues related to rate limits, quotas, and token usage reporting
    on Jul 2, 2026
  2. daveladouceur commented on Jul 23, 2026

    @daveladouceur

    I am saying the same thing everything was fine until they started to monkey around with the 5 hour limit and then started doing this usage resets nothing works everything is draining so fast I'm probably gonna have to go back to Claude - I'm not gonna mess around with poor quality that can't get done or limits my rate.

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