Skip to content

Desktop app says "new rate limit reset available" but no additional reset is credited #37396

Open

Description

@Cybernok

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

26.803.41515 (build 6321)

What subscription do you have?

ChatGPT Pro (£200/month)

What platform is your computer?

Darwin 25.5.0 arm64 arm

What issue are you seeing?

On 7 August 2026 at approximately 07:25 BST, the Codex desktop app displayed the banner: “You have a new rate limit reset available — You were granted a rate limit reset that will expire in 30 days.”

However, the Usage panel still showed only 1 available reset: an older Full reset expiring 12 August 2026 at 18:59 BST.

After restarting the app, the count remained 1. I then redeemed that existing reset because my weekly allowance had only 8% remaining. The weekly allowance correctly returned to 100% with the next reset on 14 August, but the available-reset count disappeared entirely.

The account therefore went from 1 available → 0 available, rather than 2 available → 1 available. The newly advertised 30-day reset was never added to the account.

Image Image

What steps can reproduce the bug?

  1. Open the Codex desktop app while one previously banked Full reset is available.
  2. Receive the banner saying: “You have a new rate limit reset available” and that it expires in 30 days.
  3. Open Usage and observe that the available count remains 1 rather than increasing to 2.
  4. Completely quit and reopen the app; the count still remains 1.
  5. Redeem the existing older reset.
  6. Observe that weekly usage returns to 100%, but the banked-reset count falls to zero and the newly advertised reset is absent.

Uploaded diagnostic feedback/session ID: 019fdae6-8497-7e92-b0e0-4b16af376b64

What is the expected behavior?

When the app announces that a new banked rate-limit reset has been granted, the available count should increase from 1 to 2. After redeeming the older reset, one newly granted reset should remain available with an expiry approximately 30 days from 7 August 2026.

Please verify whether the advertised reset was granted and restore it if the account was unintentionally missed.

Additional information

Account time zone: Europe/London (BST).

The exact banner wording produced no existing GitHub issues in repository search. Issue #36170 concerns a different missed reset announcement and does not describe this direct in-app grant notification followed by a 1 → 0 banked-reset count.

Private account details are intentionally omitted from this public report. Two clean screenshots are attached above; the uploaded session contains the diagnostic logs.

Activity

  1. added
    appIssues related to the Codex desktop app
    on Aug 7, 2026
  2. github-actions commented on Aug 7, 2026

    @github-actions
    Contributor

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

    Powered by Codex Action

  3. added
    bugSomething isn't working
    rate-limitsIssues related to rate limits, quotas, and token usage reporting
    on Aug 7, 2026
  4. ozgrez-bit commented on Sep 10, 2026

    @ozgrez-bit

    I'm experiencing the same issue on Windows with ChatGPT Pro on September 10, 2026.

    The Codex desktop app displays a banner saying a new rate-limit reset is available and expires in 30 days. However, the available-reset list contains only three existing resets:

    • Granted August 22, expires September 21.
    • Granted September 4, expires October 4.
    • Granted September 5, expires October 5.

    An account-status check also returned these same three available resets, with no newer grant. No reset was redeemed during this check.

    Could you clarify whether the banner is being shown incorrectly or a reset grant is missing?

  5. MuMuH1202 commented on Oct 11, 2026

    @MuMuH1202

    I am seeing the same issue on ChatGPT Pro in the native Windows Codex desktop app. As of October 11, 2026 (GMT+8), this is the second occasion on which I have received a banner saying:

    You have a new rate limit reset available. You were granted a rate limit reset that will expire in 30 days.

    However, the Usage → Rate limit resets panel still shows Available: 2, with only these existing full resets:

    • October 30, 2026, 03:04 (GMT+8)
    • November 7, 2026, 07:33 (GMT+8)

    There is no additional reset entry with an expiration around November 10, 2026, corresponding to the latest notification. My weekly allowance is also at 7% (scheduled to reset October 14), but I have not used any banked reset to test this, because doing so would consume a real credit.

    Since I have seen the award banner twice while the available count remains at 2, could the team please investigate whether this reflects (a) a repeated/incorrect notification for an existing grant, (b) a grant event that was not credited to the account, or (c) a display/synchronization problem? Please check the actual banked-reset grant ledger against notification events. I am not assuming two extra grants were due until those events are verified.

    I have screenshots of both the new-grant banner and the expanded Usage panel and can supply them through an appropriate private support channel if needed. I would appreciate guidance on how to get my account's grant history checked and any missing eligible credit restored.

    Update (October 12, 2026): I verified the client using a contemporaneous Windows Codex desktop diagnostic log, which identifies packaged App version 26.1007.2314.0 (build 13901). The full-window screenshots were captured at ~11:45:36 (banner visible) and ~11:45:52 (only 2 banked resets), GMT+8. The client successfully authenticated and subscribed to the app_notifications topic at ~11:43:38/11:43:43, but its local log does not expose a grant ID or a banner-delivery payload. Support confirmed the latest ledger grant was Oct 8, 07:33 GMT+8, with no new grant on Oct 11, but cannot inspect banner notification events. Engineering correlation between notification delivery and grant identifiers is therefore still needed; these client observations alone do not establish any missing entitlement. Full screenshots and a sanitized log timeline have been provided privately to support.

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