Pro account: 5-hour usage bucket disappeared from Codex App and account/rateLimits/read

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

26.707.8168.0

What subscription do you have?

ChatGPT Pro

What platform is your computer?

Microsoft Windows NT 10.0.26200.0 x64

What issue are you seeing?

The 5-hour usage row disappeared from the Codex App Usage dialog. The dialog now shows only the weekly usage limit and a Full reset credit.

The local app-server data changed at the same time: the 300-minute bucket is no longer returned. The weekly 10,080-minute bucket is returned as primary, while secondary is null.

Sanitized snapshots from the same running Codex task:

Before, at 2026-07-12 22:11:55 UTC:

{
  "primary": {
    "usedPercent": 74,
    "windowDurationMins": 300
  },
  "secondary": {
    "usedPercent": 16,
    "windowDurationMins": 10080
  }
}

After, at 2026-07-12 22:15:43 UTC:

{
  "primary": {
    "usedPercent": 16,
    "windowDurationMins": 10080
  },
  "secondary": null
}

A current read still has the weekly bucket only:

{
  "planType": "pro",
  "rateLimitReachedType": null,
  "primary": {
    "usedPercent": 22,
    "windowDurationMins": 10080
  },
  "secondary": null
}

The change occurred approximately four hours before the local Codex App package was updated, so it does not appear to have been introduced by that local package update.

I cannot determine from this evidence whether enforcement of the 5-hour window also changed. This report is specifically about the missing 300-minute bucket and the resulting loss of visibility.

The current official Codex pricing documentation still describes a shared 5-hour usage window plus additional weekly limits:
https://developers.openai.com/codex/pricing

What steps can reproduce the bug?

1. Sign in to Codex App with a ChatGPT Pro account.
2. Open the Usage dialog.
3. Observe that only the weekly limit is displayed; the 5-hour row is absent.
4. Start codex app-server, initialize the JSON-RPC session, and call account/rateLimits/read.
5. Observe that the only Codex usage bucket has windowDurationMins: 10080 and secondary is null; no 300-minute bucket is present.
6. Restart Codex App and repeat the check. The 5-hour row remains absent.

No usage reset was consumed to test this, and no account or configuration changes were made.

What is the expected behavior?

If the documented 5-hour window still applies, both usage buckets should be returned and displayed:

• 300-minute / 5-hour usage
• 10,080-minute / weekly usage

If this was an intentional product change, the Usage dialog, app-server contract, and official pricing documentation should consistently explain the replacement behavior.

Additional information

I searched open and closed issues before filing.

Related, but not exact duplicates:

• #32493 reports quota percentages dropping without activity; its buckets remain visible.
• #24445 reports both buckets being null on a Business plan and an incorrect out-of-messages banner.
• #24080 confirms the prior account/rateLimits/read shape with 300-minute primary and 10,080-minute secondary buckets.

Question: was the 300-minute bucket intentionally removed for Pro accounts, or is this a backend/app-server regression?