Codex Cancels 5-Hour Limit: Don't Get Too Excited, the Ceiling Is Still There

12 minutes, 40% quota gone.

That's a real record from Reddit user r/codex — running GPT-5.4 high reasoning for 12 minutes burned nearly half of the 5-hour window. Another Business user reviewing a 20K document consumed 4.2% of their 5-hour quota in a single call.

On July 12, Codex lead Tibo tweeted (1.5M views) announcing three things at once:

1. Temporarily removing the 5-hour usage limit for all Plus, Business, and Pro plans
2. GPT-5.6 Sol is undergoing comprehensive efficiency optimization, consuming less quota for the same tasks
3. Active users surpass 6 million, with a quota reset executed for everyone within one hour

The next day, an additional reset card was issued.

Social media erupted with celebration. But looking past the hype: The hourglass is gone, but the ceiling is still there.

What exactly is the 5-hour limit mechanism?

First, let's clarify what this "5 hours" actually is.

It's not a literal 5-hour timer. Under the hood, it meters tokens — input tokens, output tokens, reasoning tokens — all converted into quota consumption. The model you choose, reasoning level, context length, and codebase size all affect consumption speed.

"5 hours" is just the name of a rolling window. Once the quota inside the window is used up, you have to wait for the window to reset. The problems:

• Consumption speed is unpredictable. The same operation can consume 3x more with GPT-5.4 high compared to GPT-5.4-mini. You never know how much is left after a run.
• The window starts from the first message. Asking a casual "what does this function mean" in the morning ignites the window. By the afternoon when you need to do real work, the quota is already counting down.
• Compounds with weekly caps. Even if the 5-hour window isn't exhausted, you might hit the weekly cap. Both limits are independent; whichever hits first stops you.

So users feel: Being timed by two hourglasses simultaneously, whichever runs out first is the same.

Pricing structure: 6 tiers, 6 experiences

Most absurd is Business. Annual subscribers get 60% lower quota than Plus monthly users — someone in the OpenAI community bought 6 Business annual seats, and after the 5-hour limit revision, the work they could do shrank by 10-15x.

More striking: a Business user reviewing a 20K document in a single call translates to an actual token cost of ~$31/M. Meanwhile, OpenAI API input token price is $2.5/M. That's a 12x premium.

Community real data: How fast quota burns

Actual measurements from the OpenAI community and Reddit:

• 40% burned in 12 minutes: GPT-5.4 high reasoning, 5-hour window (Reddit)
• 4.2% per single document review: 20K document, Business plan (OpenAI community)
• 77% weekly cap consumed in 2 days: Reset on July 11, already at 77% by early July 13, even Pro 20x wasn't enough (source article author's account)
• 5-hour limit hit in 10 minutes: Workplace plan user (OpenAI community)

These numbers explain why Tibo's tweet got 1.5M views — user frustration runs deep.

After removing the 5-hour limit, what remains?

Tibo's original wording: "temporarily removing" — not permanently removing.

After removing the 5-hour window, the limit system becomes:

• Weekly cap becomes the sole ceiling. Without the rolling 5-hour window, you could theoretically use all your weekly quota in one day — then wait a week.
• Consumption speed remains opaque. Codex's usage panel shows only a progress bar, no token-level breakdown. You don't know how much each call costs, how much context takes, or how much tools calls and Skill/MCP consume. The source article author calls for Codex to show visual proportional breakdown like Zcode, but no timeline exists.
• GPT-5.6 Sol efficiency optimization is a genuine improvement. Same tasks consume fewer tokens, effectively expanding capacity. But "exact savings are pending quantification and will be announced later" — no numbers yet.

Official suggestion: Switch to GPT-5.4-mini for daily tasks, extending quota by 2.5-3.3x. It's pragmatic advice, but equates to admitting the flagship model is too expensive to use.

How competitors handle it

Codex's core advantage is model capability — GPT-5.6 Sol leads in coding agent benchmarks. But its limit system is the most complex: rolling window + weekly cap + model variance + reasoning level variance — users can't calculate how much they have left.

The sobering cost

"Temporarily removed" is not "permanently removed". Tibo used "temporarily removing", not "permanently removing". The 5-hour limit could return at any time — in an optimized form.

Weekly cap is the true ceiling. After removing the 5-hour window, the weekly cap goes from "one of two safeguards" to "the only constraint". Users might burn through the weekly quota in the first two days, then wait five days. The experience shifts from "frequent interruptions" to "a single longer interruption".

Pricing inversion remains unsolved. The issue of Business getting 60% lower quota than Plus wasn't addressed by Tibo. Annual subscribers are locked into low quotas with no exit mechanism.

Opacity is the root cause. A progress bar is not data. Users need token-level consumption details — context, tool calls, Skills, MCP breakdown — not a vague percentage.

Old models not discounted. GPT-5.4, GPT-5.3 could easily be discounted to promote cheap models for daily tasks and flagship models for critical work. But OpenAI hasn't done this.

Judgment

Removing the 5-hour limit is good, but it's just dismantling one hourglass — the ceiling remains.

Three real solutions:

1. Permanently remove the 5-hour window, keep only the weekly cap, simplify the limit system
2. Token-level consumption transparency, let users know where money goes
3. Discount older models, cut GPT-5.4-mini and GPT-5.3 by 30-50%, use cheap models for daily tasks

Until then, pragmatic strategy: use GPT-5.4-mini for daily tasks (2.5-3.3x quota extension), GPT-5.6 Sol for critical tasks, plan quota allocation early in the week — don't burn through the weekly cap in the first two days.

After all, the hourglass is gone, but the ceiling is still there.