Codex Plus can stop work with 84% of weekly usage left
OpenAI's five-hour gate can interrupt concentrated Codex work while weekly usage remains. It limits when Plus can work, not necessarily total usage.
On this page
Codex Plus can stop new included work at its five-hour limit even while the weekly meter has room. One Reddit user reported that a 28-minute Sol High task left 84% of weekly usage untouched. The report shows the practical effect of two separate caps, but it cannot tell us whether OpenAI reduced the weekly allowance. [2] [5]
OpenAI restored the Plus gate on 26 August 2026
OpenAI engineering lead Thibault Sottiaux announced on 25 August 2026 that the five-hour limit would return for Plus accounts across Codex and ChatGPT Work the next day. An earlier return had been announced and postponed. His new announcement restored that shorter gate. [1]
Sottiaux gave two reasons for the shorter window. First, spreading demand over time lets OpenAI smooth the load on its compute while keeping the weekly plan generous. Second, he said relatively casual and new Plus users could accidentally consume their full weekly allowance and then be confused by the lockout. The five-hour gate is therefore both a capacity control for OpenAI and a spending guardrail for the subscriber. Whether that guardrail helps depends on how the subscriber works. [1]
The same announcement said the $100 and $200 Pro subscriptions would keep the five-hour gate disabled for the “upcoming months”. That was a temporary policy for those two subscriptions, not a permanent plan entitlement. [1]
This article follows my earlier investigation of Codex usage resets, but the new issue is different. Whereas the July 2026 campaign changed available usage through resets, this gate changes when a Plus user can spend the included usage that remains.
Why can Codex stop work with weekly usage left?
The five-hour window and the weekly allowance are separate controls. A Plus account must have room in both to keep starting included Codex or ChatGPT Work usage. Reaching the shorter limit can therefore stop new work even while the weekly meter still shows capacity. [2] [3]
OpenAI’s current pricing page says local messages and cloud tasks share a five-hour window and that additional weekly limits may apply. Its help center tells users who reach a limit to check which allowance is exhausted and the reset time shown in the usage dashboard or limit notice. Those instructions only make sense if more than one allowance can be the blocker. [2] [3]
| Question | Five-hour window | Weekly allowance |
|---|---|---|
| What does it control? | Usage inside the shorter period | Total included usage across the week |
| Where is the reset time? | Usage dashboard or limit notice | Usage dashboard or limit notice |
| What happens when it is exhausted? | Included plan usage resumes after this reset | Included plan usage resumes after the weekly reset |
| What did the 25 August 2026 announcement establish? | The gate returned for Plus | No weekly reduction was documented |
A non-empty weekly meter does not override an exhausted five-hour window. The inverse is also true: a refreshed short window cannot restore a weekly allowance that has already run out.
What does the 84% Reddit meter actually prove?
The 84% report shows how far the two meters can diverge on one Plus account. Its author said a 28-minute, 29-second Sol High task exhausted the five-hour allowance while 84% of weekly usage remained. It does not establish a universal burn rate or a weekly cut. [5]
The wider Reddit evidence supports a different conclusion: the returned gate caused visible confusion and objections to interrupted work. At the research capture on 27 August 2026, the main r/codex announcement thread had about 820 upvotes, while three related discussions had about 608, 382, and 379 upvotes across r/codex and r/ChatGPT. These changing snapshots show activity across four threads, not the share of subscribers who objected. [4] [5] [6] [7]
Another thread focused less on consumption and more on notice. Its author argued that a user who did not follow social media could have missed both the temporary nature of the earlier policy and the announcement that the limit was returning. The r/ChatGPT discussion contains the resulting basic questions: whether the limit is daily or weekly and whether it covers only Codex. Those questions show that the policy was not self-explanatory to those commenters. [6] [7]
The gate protects capacity but interrupts concentrated work
My read is that the five-hour gate makes Plus less useful for developers who deliberately reserve one long block for a large change. The weekly amount can remain unchanged while the session still loses continuity.
That is the practical trade-off in Sottiaux’s explanation. Spreading work protects shared capacity and can stop a casual user from consuming a week by accident, but it also limits a deliberate user who wants to spend the same allowance in one sitting. [1]
No single task tells the rest of us how quickly the gate will close. OpenAI says usage depends on the model, where the task runs, task complexity, context, reasoning, speed, and tools. A long-running request can cost substantially more than a short one, and two tasks that look similar can take different paths through a repository. The 28-minute Reddit report is useful because it shows the interruption, not because 28 minutes is a reusable estimate. [3] [5]
The announcement documents a scheduling control. I found no evidence in the cited material that Sol became slower or that OpenAI changed how tokens map to plan usage.
How should I plan around the Codex five-hour limit?
Start with the two live meters, not an estimate copied from somebody else’s task. Open the Codex usage dashboard before a large session, note which allowance is closer to exhaustion and record each displayed reset time. In an active Codex CLI session, /status shows the remaining limits. [2] [3]
I would then give the session a task boundary that can produce a useful checkpoint before the shorter allowance runs out. For a large change, that might mean separating repository analysis from implementation, or asking for one tested slice before opening the next slice. Check the meter again after a long planning or tool-heavy phase. If the five-hour allowance is low, stop before starting another broad change. Your own recorded sessions provide a more useful threshold than somebody else’s percentage.
If a limit is reached during an active turn, OpenAI says Codex can continue that turn subject to fair-use limits. After it finishes, the usage page or banner can offer the options available to that account, such as waiting for the displayed reset, adding credits, applying an eligible reset, or upgrading. “Can continue” is not a guarantee that every long task always finishes, so I would still preserve a tested checkpoint before the meter reaches zero. [3]
I use this as a planning method, not a burn-rate formula, because I did not record both meters on a controlled Plus account for this article. A useful personal estimate begins only after you record several comparable tasks with the model, effort, client, repository, and tools held as steady as possible.
What would prove that OpenAI cut weekly usage?
Only matched tasks across two full weeks could show whether OpenAI cut the weekly allowance after 26 August 2026.
Capture both meters before and after each task on the same Plus account, without credits or resets, while keeping the model, effort, client, repository, and tools fixed. That extends the method from my earlier reset investigation by separating a five-hour block from weekly consumption.