Skip to content

Usage UI should show special Codex rate-limit reset events and affected quota intervals #20583

@jjoanna2-debug

Description

@jjoanna2-debug

What variant of Codex are you using?

Codex for macOS

What version of the Codex App are you using?

Version 26.429.20946

What subscription do you have?

Plus

What platform is your computer?

macOS Tahoe

What issue are you seeing?

When a special Codex rate-limit reset is announced or applied, the Codex Usage UI does not show any reset-event record or affected quota scope.

This creates an unresolved product-transparency problem: users cannot tell whether a special reset reached their account, which quota interval was affected, or whether a visible quota interval was intentionally excluded.

This is not a request for more usage, credits, or a general usage-status feature. It is a narrower request for reset-event visibility.

Context:

  • Issue Clarify Codex rate-limit reset behavior and make reset scope visible in Usage UI #20395 was closed as completed, with a comment stating that the suggestions were already covered by other feature requests.
  • No specific duplicate issue was linked that covers special reset-event history or reset-scope visibility.
  • I have also escalated the related account-specific concern through OpenAI Support under case number 08300824.
  • The support path has not provided a substantive product-level resolution to the reset-scope visibility problem.

The specific public communication that triggered this was a Codex rate-limit reset announcement for “ALL paid plans”:

https://x.com/thsottiaux/status/2048997818673537399?s=46&t=T-QN-YBrEo1iiw5oRoIM_Q

Support later described the operational behavior as narrower than the public wording: reset behavior depended on quota interval, account state, usage timing, and technical eligibility, and the weekly Codex limit was not reset for my Plus account.

That may be intended backend behavior. The product issue is that the Usage UI gives users no way to verify the special reset event or its scope.

What steps can reproduce the issue?

  1. Use Codex on a paid account with active usage already consumed.
  2. A special Codex rate-limit reset is announced or applied.
  3. Open Codex Usage.
  4. Review the visible quota intervals, such as the shorter rolling window and the weekly limit.
  5. Observe that the UI does not show:
    • whether a special reset event was applied to the account;
    • when the reset event was applied;
    • which quota interval(s) were affected;
    • which quota interval(s) were excluded;
    • whether reset eligibility depended on backend account state, timing, threshold, or quota type.

What is the expected behavior?

Codex Usage should display reset-event information when a special quota reset is applied or announced for users.

For example, the Usage UI could show a small reset-event record such as:

  • Special reset applied: Apr 28, 2026, 06:28
  • Affected interval: 5-hour window
  • Excluded interval: weekly limit
  • Scope: eligible paid-plan accounts / eligible quota states

If no special reset was applied to the account, the UI should also make that clear rather than leaving users to infer the result from ordinary timer behavior.

Actual behavior

The Usage UI only shows the ordinary quota state and reset timers. It does not distinguish between:

  • an ordinary scheduled quota refresh;
  • a special reset that successfully propagated;
  • a special reset that applied only to selected quota intervals;
  • a special reset that did not apply to the account;
  • a reset implementation that depends on backend eligibility.

Why this matters

Codex exposes multiple visible usage intervals. When a special reset is publicly announced, users need a way to verify the reset event and its scope inside the product.

Without reset-event visibility, users cannot determine whether the product is behaving correctly, whether support needs to investigate propagation, or whether the reset intentionally excluded a visible quota interval.

This also creates avoidable support escalations. In my case, the account-specific escalation is already under Support case number 08300824, and I have separately raised the EEA/Portugal consumer-transparency concern there. This GitHub issue is not asking maintainers to decide that support dispute. It is asking for the missing product-level visibility that would prevent this ambiguity in the first place.

Requested improvement

Please add reset-event visibility to Codex Usage for special rate-limit resets:

  1. show whether a special reset event applied to the account;
  2. show the reset timestamp;
  3. show the affected quota interval(s);
  4. show excluded quota interval(s), if any;
  5. distinguish special reset events from ordinary scheduled quota refreshes.

Additional information

Related prior issue: #20395

This issue is intentionally narrower than #20395. It is focused only on special reset-event visibility and affected quota scope in the Codex Usage UI.

Metadata

Metadata

Assignees

No one assigned

    Labels

    appIssues related to the Codex desktop appenhancementNew feature or requestrate-limitsIssues related to rate limits, quotas, and token usage reporting

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions