Five-hour Codex usage limit disappeared from Plus account; only weekly limit is shown
What version of the Codex App are you using (From “About Codex” dialog)?
Latest codex desktop app
What subscription do you have?
plus
What platform is your computer?
Darwin 24.0.0 x86_64 i386
What issue are you seeing?
My ChatGPT Plus account previously displayed both a five-hour Codex usage limit and a weekly usage limit.
The five-hour limit has now completely disappeared from the Codex app. The account currently displays only a weekly allowance, for example:
Weekly usage remaining: 79% — resets July 20
There is no five-hour usage meter shown anywhere, and Codex tasks appear to consume the weekly allowance directly.
This follows an earlier usage issue on the same account. Before that incident, the interface showed approximately:
- 75% of the five-hour allowance remaining
- 90% of the weekly allowance remaining
During a single long-running Codex task, both limits suddenly dropped to zero. The task stopped, the limits later briefly returned, and then disappeared again.
The current persistent issue is that the five-hour limit is no longer displayed at all.
I am using an active ChatGPT Plus subscription. I was not using Fast mode, image generation, multiple concurrent Codex sessions, or other parallel agent activity when the earlier depletion occurred.
This may be one of the following:
- An account-entitlement or provisioning issue
- A usage-meter display bug
- An incorrect limit configuration
- A usage-ledger synchronization issue
- The account being assigned a weekly-only limit despite having Plus
Expected behavior:
The Codex app should display and enforce the correct usage limits associated with my ChatGPT Plus subscription. If a five-hour allowance applies, it should remain visible and its remaining usage should be accurately reported.
Actual behavior:
Only the weekly limit is visible. The five-hour meter that was previously present has disappeared completely.
I have screenshots showing the weekly-only usage display and can attach them to this issue.
Please investigate whether the correct Codex Plus entitlements and usage-limit configuration are attached to my account.
What steps can reproduce the bug?
Feedback ID: 019f51ce-68d9-7801-bd94-6781d744c75c
What is the expected behavior?
The Codex app should display and enforce the correct usage limits for an active ChatGPT Plus subscription.
If my account is entitled to both a five-hour limit and a weekly limit, both should remain visible in the usage interface and update accurately after each task.
The five-hour meter should not disappear without explanation, and the app should not suddenly switch to showing only a weekly allowance.
Usage should also remain consistent across app restarts and sign-ins, without limits unexpectedly dropping to zero, briefly returning, and then disappearing again.
Additional information
This is not simply a complaint that one task consumed more usage than expected.
The main issue is that my account previously displayed both a five-hour limit and a weekly limit, but the five-hour limit has now completely disappeared.
Before the earlier incident, I had approximately:
- 75% of the five-hour limit remaining
- 90% of the weekly limit remaining
During one Codex task, both limits suddenly dropped to zero. They later briefly returned, then disappeared again.
The current persistent state is that only the weekly limit is shown, and Codex usage appears to be deducted directly from that weekly allowance.
I am using an active ChatGPT Plus subscription. I was not using Fast mode, image generation, or multiple parallel Codex sessions.
Feedback ID: 019f51ce-68d9-7801-bd94-6781d744c75c
I have screenshots showing the weekly-only meter and the missing five-hour limit.
12 Comments
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
This is expected behavior right now, not an account/entitlement bug.
On Jul 12, Tibo (Codex lead) announced they are temporarily removing the 5-hour usage limit for all Plus, Business and Pro plans, alongside GPT-5.6 Sol efficiency improvements and a usage reset: https://x.com/thsottiaux/status/2076365965915467978
With the 5-hour window disabled there's nothing for that meter to track, so the app only shows the weekly allowance, which matches your "Weekly usage remaining: 79% — resets July 20" screen. The earlier blip where both limits dropped to zero and came back also lines up with the launch-week load issues and the quota reset they pushed around the same time.
The 5-hour meter should reappear if/when they re-enable that limit.
Right thank you for clarifying that out. Now when I should expect my limits to be reset back what they once where ?
Get Outlook for iOS<https://aka.ms/o0ukef>
________________________________
From: Fandu @.*>
Sent: Monday, 13 July 2026 16:04:34
To: openai/codex @.*>
Cc: Mohamed Elhadj, Sidi Mohamed [60307289] @.>; Author @.>
Subject: Re: [openai/codex] Five-hour Codex usage limit disappeared from Plus account; only weekly limit is shown (Issue #32791)
[https://avatars.githubusercontent.com/u/113630375?s=20&v=4]mrfandu1 left a comment (openai/codex#32791)<https://github.com/openai/codex/issues/32791#issuecomment-4958242513>
This is expected behavior right now, not an account/entitlement bug.
On Jul 12, Tibo (Codex lead) announced they are temporarily removing the 5-hour usage limit for all Plus, Business and Pro plans, alongside GPT-5.6 Sol efficiency improvements and a usage reset: https://x.com/thsottiaux/status/2076365965915467978
With the 5-hour window disabled there's nothing for that meter to track, so the app only shows the weekly allowance — which matches your "Weekly usage remaining: 79% — resets July 20" screen. The earlier blip where both limits dropped to zero and came back also lines up with the launch-week load issues and the quota reset they pushed around the same time.
The 5-hour meter should reappear if/when they re-enable that limit.
—
Reply to this email directly, view it on GitHub<https://github.com/openai/codex/issues/32791?email_source=notifications&email_token=CBHAXYCKAXEHC7W324RL3ZL5ETM6FA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTIOJVHAZDIMRVGEZ2M4TFMFZW63VGMF2XI2DPOKSWK5TFNZ2KYZTPN52GK4S7MNWGSY3L#issuecomment-4958242513>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/CBHAXYCRRMB5DOQL2HTHD6T5ETM6FAVCNFSNUABFKJSXA33TNF2G64TZHM4TMNJUGE2TMNBZHNEXG43VMU5TIOBXGM4DMNBXGQ32C5QC>.
Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS<https://github.com/notifications/mobile/ios/CBHAXYBCDNJ5EWC5YLRXVWL5ETM6FA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTIOJVHAZDIMRVGEZ2M4TFMFZW63VGMF2XI2DPOKSWK5TFNZ2KUZTPN52GK4S7NFXXG> and Android<https://github.com/notifications/mobile/android/CBHAXYDAOAHJJXCHKUJPH535ETM6FA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTIOJVHAZDIMRVGEZ2M4TFMFZW63VGMF2XI2DPOKSWK5TFNZ2K4ZTPN52GK4S7MFXGI4TPNFSA>. Download it today!
You are receiving this because you authored the thread.Message ID: @.***>
The effective context window shrunk since yesterday as well from new 350k -> down to old 250k. Is it related?
What are they thinking???
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.
It was probably the reset happened and I was at 0%. if they don't solve this im unsubbing and never subbing back again.
I burned all tokens even without releasing that on start of seek because of this.. Pretty bad decision intentional or not will it will be problem to power users on budget.
<img width="1000" height="780" alt="Image" src="https://github.com/user-attachments/assets/7b3bc10c-1052-45c3-84bb-8ba2f2971d22" />
<img width="287" height="240" alt="Image" src="https://github.com/user-attachments/assets/aea6d532-2ad2-4903-bcd9-18257af05ed2" />
<img width="1085" height="670" alt="Image" src="https://github.com/user-attachments/assets/644d198b-389c-48a0-905f-0430ba313f06" />
I can confirm the same missing five-hour usage bucket on a ChatGPT Plus account, but my case also suggests that this may be more than a display-only problem.
Environment
The five-hour limit is absent from:
/statusMy CLI
/statusoutput shows only:During a session of approximately three hours, around 81% of my weekly allowance was consumed. I did not encounter a five-hour-limit warning, reset or interruption at any point.
Therefore, my concern is not only that the 300-minute meter is hidden. The five-hour limit also does not appear to be acting as a meaningful intermediate cap before most of the weekly allowance can be consumed.
/usage dailyonly displays historical token activity, includingLifetime 783M, and does not provide a breakdown of what was charged during the affected session or how it translated into the weekly percentage.Related report about the accelerated weekly depletion:
https://github.com/openai/codex/issues/33685
Please investigate whether the 300-minute bucket is still provisioned and enforced for Plus accounts and whether the weekly usage accounting changed when that bucket disappeared.
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.
As you see nobody cares in OpenAI, this was a deliberate decision.
OpenAi team should wake up sooner or later. Now still you can feel like you are on top of the world and anything will be accepted by consumers, but clock it ticking. I already see this platform as unreliable, yet I still can do some workarounds to mitigate this to my advantage, after I cant anymore bye, bye. You already are replaceable.
Adding another Plus account data point because the missing 5-hour meter is still affecting day-to-day use and makes the current limits very hard to reason about.
Environment:
Observed behavior:
I also contacted OpenAI Support (Case 13389340). Support told me that the limited-time 2x promotion ended, that the pre-promotion 5-hour session limits were reduced while weekly limits were increased, and that users may now reach the 5-hour limit sooner. That makes the missing UI especially confusing: if the 5-hour limit still exists and can be reached sooner, users need to be able to see its remaining percentage and reset time.
The core request is simple:
This is not just cosmetic. Without the 5-hour meter, it is impossible to plan a workday or distinguish short-window depletion from weekly depletion. Related accelerated-weekly-drain report: #33685.