OpenAI restores 5-hour Codex and Work limits for ChatGPT Plus

The five-hour window is back for Plus

OpenAI is restoring the five-hour usage limit for ChatGPT Plus accounts using Codex and ChatGPT Work, with the change applying across both surfaces after a period in which the five-hour cap had been temporarily lifted [1]. The announcement came from Thibault “Tibo” Sottiaux, OpenAI’s engineering lead for Codex and ChatGPT, who said the cap would return for Plus users and described the decision as necessary to smooth compute load while keeping weekly usage comparatively generous [1].

9to5Mac reported the change late on August 24, noting that the restored five-hour limit applies to Codex and ChatGPT Work for Plus subscribers starting on August 25 [2]. The report also said users who hit either the five-hour or weekly limit can wait for the next reset cycle or purchase additional credits, while OpenAI may occasionally reset usage limits for free and some users may have banked resets from promotions or referrals [2].

The practical meaning is straightforward: Plus users again face two constraints rather than one. A session can be interrupted by a short-window usage ceiling even if a user still has weekly allowance remaining; conversely, a user who burns through the weekly allowance can be blocked even if a five-hour window would otherwise refresh. That dual structure is familiar to many developers who used Codex earlier this year, but it is a noticeable reversal for users who had adjusted to a weekly-only rhythm during the temporary pause [2].

Why OpenAI says it is doing this

Sottiaux gave two main reasons for the restoration. First, he said a five-hour cap helps smooth demand on OpenAI’s compute infrastructure, which matters because agentic coding and work sessions can be long-running and expensive compared with ordinary chat [1]. Second, he argued that Plus users are often relatively casual or new users who can accidentally consume an entire week of usage in a burst, creating confusion and a poor experience when they are suddenly locked out for days [1].

That explanation points to a core tension in consumer AI subscriptions. Developers often want freedom to run a long refactor, debugging session, migration, or research task in one sitting. The provider, however, has to manage a shared pool of inference capacity across millions of users and across increasingly agentic products. A five-hour window is a blunt but understandable instrument: it limits bursts, spreads demand, and reduces the likelihood that a single evening of experimentation drains a full week of included usage.

The restored cap is not being applied uniformly to every paid consumer tier. Sottiaux said OpenAI is keeping the five-hour limit disabled for Pro $100 and Pro $200 subscriptions for the upcoming months [1]. That creates a sharper distinction between Plus and higher Pro tiers: Plus remains the low-cost entry point for “a few focused coding sessions,” while Pro is positioned for longer and heavier daily work [2].

What changed during the temporary pause

During the temporary lifting of the five-hour limit, many users were governed mainly by weekly usage. 9to5Mac described the past several weeks as a period in which OpenAI left only the weekly cap in place for Codex and ChatGPT Work [2]. The same report said OpenAI also reset users’ weekly usage early several times during that period, including resets tied to milestones across the now-unified Codex and Work platforms [2].

That experiment solved one problem while exposing another. Without a five-hour window, users could run longer continuous sessions and use more of their weekly allocation at once. For power users, that meant fewer forced pauses and less context-switching. For less experienced users, it also made it easier to exhaust the weekly pool without realizing how much a long agentic run, high-reasoning setting, broad repository context, or multiple tool calls were consuming.

OpenAI’s current Help Center language underlines that usage depends on model choice, task location, task complexity, context, reasoning, speed, and tools, and that a long-running task can consume substantially more than a short request [3]. That is the important product reality behind the limit debate: in agentic systems, a “message” is not always a small event. One instruction can trigger planning, code edits, terminal commands, browsing, app actions, tests, retries, and additional model calls.

Codex and Work share the same pool

OpenAI’s Help Center currently says Codex is included across ChatGPT plans, but usage limits vary by plan [3]. It also says Codex, ChatGPT Work, ChatGPT for Excel, and Workspace Agents use a shared allowance and credit pool when those features are available on a user’s plan [3]. This shared-pool design matters because users may think of Codex and Work as separate products, when in practice heavy use in one can reduce available headroom in the other.

The Help Center advises users who are nearing or have reached a Codex limit to check Settings or the usage dashboard, review which allowance is exhausted, look at credit balance and reset time, and use /status inside an active Codex CLI session [3]. It also says users may be able to add credits, use an available reset, upgrade, or wait until the displayed reset time, depending on what their account offers [3].

This is where transparency becomes essential. When the product presents both short-window and weekly constraints, users need to know which one they hit, when it resets, how much of the weekly allowance remains, and whether a banked reset or paid credit purchase is more rational than waiting. OpenAI’s documentation says a banked full reset can reset both five-hour and weekly windows and move the weekly reset date to roughly seven days after redemption [3]. That is valuable, but it also means users must treat resets as scarce and time-sensitive rather than as a casual refresh button.

Why developers are split

Reaction among users is divided. A Reddit thread posted shortly after the announcement framed the change as a disappointment for Plus subscribers, with some commenters arguing that the weekly limit already felt restrictive and that bringing back the five-hour window would make Codex less useful for sustained coding sessions [4]. Other users in the same discussion acknowledged that the five-hour limit can act as a guardrail, preventing an entire weekly allocation from disappearing in a single burst [4].

Both sides have a point. Developers doing concentrated work dislike artificial pauses because coding momentum is fragile. A five-hour reset can arrive after the mental context has faded, the local branch has changed, or the user has moved to another tool. For these users, the removal of the five-hour cap felt like a productivity upgrade.

But users who accidentally burned a full weekly allocation in a few hours experienced the opposite problem. They did not feel freer; they felt trapped. A short-window cap can protect the weekly budget from one runaway session, especially when an agent is allowed to inspect a large repository, run tests repeatedly, or operate with a high reasoning setting.

The competitive angle

The change also affects how users compare OpenAI’s agentic tools with alternatives such as Claude Code, Cursor, and API-based workflows. The key comparison is no longer only model quality; it is predictability. Developers want to know how much work a subscription buys, whether limits reset clearly, whether usage is visible in real time, and whether a task will be cut off at a critical moment.

For OpenAI, the restored Plus cap may push heavier users toward Pro tiers, credits, Business, or API usage. That can be commercially rational, but it risks frustrating Plus users who joined during a more generous temporary window. The company’s messaging therefore needs to be precise: if the five-hour window is a permanent Plus design choice, users will plan around it; if it is a flexible compute-management lever, users will expect sudden changes.

The announcement also shows how agentic AI products are moving away from the simple chat subscription model. In ordinary chat, a user can count messages. In Codex and Work, a task can branch into many hidden or semi-hidden compute events. That makes usage accounting harder to communicate and harder for users to predict.

What Plus users should do now

For Plus users, the immediate adjustment is to plan Codex and Work sessions around both limits. Smaller prompts, narrower repository scope, lighter reasoning settings, fewer connected tools, and careful use of large context files can stretch the allowance [3]. Users should also check the usage dashboard before launching long tasks, especially if they are close to a reset or considering whether to spend credits [3].

The bigger lesson is that Codex and ChatGPT Work should be treated less like unlimited chat and more like a metered cloud resource bundled into a consumer plan. The return of the five-hour limit does not make the tools unusable, but it changes their rhythm. Plus is again a plan for bounded sessions, not necessarily uninterrupted all-day agentic work.

OpenAI’s decision may reduce surprise weekly lockouts and help stabilize compute demand. It may also revive frustration among developers who benefited from the temporary weekly-only model. The current state is therefore a compromise: Plus users get access to powerful agentic coding and work tools, but with a restored short-window governor that shapes when and how intensively those tools can be used [1].

Sources from the last 72 hours

1. [1]OpenAI restores 5-hour Codex and Work limits for ChatGPT Plus usersAug 25, 2026, 1:47 AM UTC
2. [2]5H limit back from tomorrow for Plus subs... : r/codexAug 25, 2026, 2:11 AM UTC
3. [3]Tibo on X: Tomorrow we will bring back the 5h limit for Plus accounts across ChatGPT Work and CodexAug 25, 2026, 1:16 AM UTC
4. [4]Using Codex with your ChatGPT plan | OpenAI Help CenterAug 24, 2026, 2:33 AM UTC

AI-generated article based on recent web research, then preserved as a dated editorial snapshot.