›_ Codex Issues
Codex Issues / #32707

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

Open 💬 10 comments Opened Jul 13, 2026 by aidawilliam41-ops
💡 Likely answer: A maintainer (github-actions[bot], contributor) responded on this thread — see the highlighted reply below.

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?

View original on GitHub ↗

10 Comments

github-actions[bot] contributor · 1 month ago

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

  • #32635

Powered by Codex Action

Lady-Lin · 1 month ago

OpenAI has removed the 5-hour limit; this is not a bug. Closing this now.

daddy32 · 1 month ago
OpenAI has removed the 5-hour limit; this is not a bug. Closing this now.

The issue is stil open; also thia statement is still contradictory with the official documentation.

topemalheiro · 1 month ago

What are they thinking???

Killka84 · 1 month ago

It appears that when the five-hour limit was removed, the quota size itself was not recalculated.

The same amount of usage that was previously available every five hours now appears to be allocated for an entire week.

In other words, it looks as if only the reset period was changed from 5 hours to 7 days, while the actual quota amount remained approximately the same.

If this is intentional, then this is not a removal of the limit. It is a major reduction in available usage, because the same quota that previously renewed several times per day now renews only once per week.

Please investigate whether the weekly quota was mistakenly configured using the former five-hour quota value.

fordicus · 1 month ago

I am observing a very similar pattern.

Since the 5-hour window disappeared and only the 7-day limit is shown, my weekly quota appears to be depleting at an extremely fast rate compared with previous usage patterns. This makes @Killka84's hypothesis highly worth investigating: it does look possible that the reset window changed from 5 hours to 7 days while the actual quota size was not recalculated accordingly.

If that is the case, this would effectively be a major reduction in usable Codex capacity rather than a simple removal or hiding of the 5-hour limit.

Could the Codex team please confirm whether the weekly quota was recalculated after the 5-hour bucket disappeared, and respond directly to this point?

Lady-Lin · 1 month ago
What are they thinking???

BCZ The cost of calling large models will soon become cheaper than water.

yukinaga-yoshida · 28 days ago

Please expose the 5-hour and weekly rate-limit reset times in the built-in Codex CLI statusline.

Requested display:

5h 82% left · 22:14
wk 97% left · 0803 09:00

On Codex CLI 0.146.0, account/rateLimits/read currently returns only the weekly 10080-minute window for my account, so the 5-hour window cannot be displayed
even though the pricing documentation describes it.

Please either:

  1. expose reset-time statusline items such as five-hour-limit-reset and weekly-limit-reset, and
  2. clarify whether the missing 300-minute window is a backend/account regression or an intentional change.

The current behavior makes it impossible to tell when the 5-hour limit resets.

ericknyoto · 17 days ago

I’m seeing the same behavior on a ChatGPT Plus account.

In Settings → Usage, only the Weekly usage limit is shown. There is no 5-hour meter or 5-hour reset information.

I also checked directly from Codex CLI v0.147.0 using /status, and it shows only:

Weekly limit: 5% left (resets 12:07 on 16 Aug)

There is no 5-hour remaining allowance or reset shown there either.

I contacted OpenAI Support and they confirmed that the public Codex documentation still describes a shared rolling 5-hour window for local messages + cloud chats, with additional weekly limits potentially applying. However, they could not confirm whether the 5-hour window is actually enforced on my specific account when neither /status nor the Usage dashboard exposes it.

So in my case, both documented user-facing rate-limit surfaces currently expose weekly usage only.

This makes it difficult to tell whether:

the 5-hour window is still active but hidden,
the account has been provisioned with weekly-only limits,
or this is a UI/entitlement/rate-limit configuration bug.

Happy to provide additional account-independent diagnostics if useful.

Since /status itself directs users to the Usage dashboard for up-to-date rate-limit information, having neither surface expose the 5-hour window makes the documented limit effectively unverifiable from the user side.

stanicio · 5 days ago

I can confirm the missing main 5-hour bucket on another ChatGPT Pro Lite account using Codex CLI 0.147.0 on Windows.

Two consecutive /status observations (Europe/Prague, CEST):

2026-08-21 22:22

  • Active model: gpt-5.6-terra
  • Main Codex weekly limit: 100% remaining, resets 2026-08-28 02:38
  • No main Codex 5-hour row was displayed
  • GPT-5.3-Codex-Spark 5-hour limit: 100% remaining, resets 2026-08-22 03:22
  • Spark weekly limit: 98% remaining, resets 2026-08-26 01:44

2026-08-22 01:28

  • I had used gpt-5.6-terra during the interval and had not selected or used Spark
  • Main Codex weekly limit: decreased to 99%, reset still 2026-08-28 02:38
  • The main Codex 5-hour row was still absent
  • Spark 5-hour limit: still 100%, but its reset moved to 06:27
  • Spark weekly limit: still 98%, reset still 2026-08-26 01:44

The observations were approximately 3 hours 5 minutes apart. The unused Spark 5-hour reset timestamp also moved forward by approximately 3 hours 5 minutes while remaining at 100% and without any Spark use. This makes the displayed Spark timestamp appear to be a continuously recalculated prospective value (current time + 5 hours) rather than the end of an active fixed window.

At the same time, actual Terra usage reduced the main weekly allowance from 100% to 99%, but the main 300-minute/5-hour bucket remained absent from /status.

This appears consistent with the missing main 300-minute bucket reported here, and it additionally raises a display-semantics question for unused model-specific buckets:

  1. Is the main 5-hour bucket intentionally omitted for this plan/account, or is the backend snapshot incomplete?
  2. Is an unused 100% Spark 5-hour timestamp intentionally prospective and expected to track the current time?
  3. If so, could the UI distinguish “window would start on first use” from an actual fixed resets_at event?

Timestamped screenshots are available and I can provide sanitized crops if useful.