429 Too Many Requests on /backend-api/wham/rate-limit-reset-credits blocks reset-credits UI in both desktop app and web (Pro)

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

Version 26.803.61601 (Released Aug 8, 2026) — "Powered by Codex & OWL"

What subscription do you have?

ChatGPT Pro

What platform is your computer?

Darwin 25.6.0 arm64 arm

What issue are you seeing?

GET https://chatgpt.com/backend-api/wham/rate-limit-reset-credits is returning 429 Too Many Requests, and this reproduces in both the desktop Codex app and the web app on the same account.

The consequences in the UI:

1. The reset-credits UI never loads — the credits/usage panel fails to populate because the request that backs it is rejected.
2. Reset credits cannot be redeemed/applied — the action that depends on this endpoint fails.
3. 429 retry loop — the client keeps re-issuing the request rather than backing off, so the failure repeats continuously instead of surfacing once.

Failing request details:

Request URL:     https://chatgpt.com/backend-api/wham/rate-limit-reset-credits
Request Method:  GET
Status Code:     429 Too Many Requests
Remote Address:  172.64.155.209:443
Referrer Policy: strict-origin-when-cross-origin
x-oai-request-id: 830faf4a-fa22-4941-98f7-231bdf217d8f

Notably this is a read endpoint for reset credits, so a 429 here blocks visibility into credits rather than throttling any expensive operation.

What steps can reproduce the bug?

1. Sign in to a ChatGPT Pro account.
2. Open the Codex desktop app (v26.803.61601) or go to the Codex web app at chatgpt.com.
3. Open the view that displays reset credits / usage limits.
4. Observe in DevTools (web) or the network log that GET /backend-api/wham/rate-limit-reset-credits returns 429, the credits UI does not load, and the request is retried repeatedly.

Reference request id: 830faf4a-fa22-4941-98f7-231bdf217d8f

What is the expected behavior?

• GET /backend-api/wham/rate-limit-reset-credits should return the account's reset-credit state for a Pro account rather than 429.
• If the endpoint genuinely must rate limit, the client should honor Retry-After and back off instead of looping, and should surface a clear, actionable error rather than an empty/stuck credits panel.

Additional information

• Reproduces on both surfaces (desktop app and web), which suggests the problem is server-side on the endpoint rather than in a single client.
• Possibly related existing reports about reset-credit/usage accounting: #37455, #37250, #30456, #30726.

Start by tracing GET /backend-api/wham/rate-limit-reset-credits from the Codex web and desktop usage views, then verify whether this repository owns the endpoint or its retry behavior. Reproduce with a Pro account and inspect the network log. Done means the reset-credit state loads, repeated 429 responses back off, and the UI surfaces a clear error when necessary.