5 hours limit is back :(

[NirNova98]

I’d strongly prefer Codex to use only the weekly usage limit, without the additional 5-hour limit.

During the period when only the weekly limit applied, Codex was much more useful for my workflow. I often have days where I need to do several hours of intensive coding, followed by days where I use very little.

The 5-hour limit can interrupt a productive coding session even when I still have plenty of weekly usage remaining.

Please consider bringing back the weekly-only usage model, or at least offering an option where users can consume their weekly allowance freely without a separate 5-hour cap.

[luxd7]

I completely agree. When using the SOL model, the five-hour usage limit is so restrictive that you can't even finish a single normal task. It used to let you carry over whatever was left and keep working, but now it just cuts you off right in the middle of things. You can't continue, and you're forced to wait five hours for it to reset before you can do anything else. The experience is just terrible. Honestly, I use up the five-hour quota in about twenty minutes, and then I have to switch to something else. If a tool doesn't even give you a solid five hours, it's just not worth using.

[Oberbaer]

The 5-hour Codex limit makes Plus much less useful for longer development sessions

I’m a ChatGPT Plus user and I regularly use Codex together with VS Code for larger development projects.

The current combination of a 5-hour usage window and an additional weekly limit is a major downgrade for this kind of workflow.

The core problem is simple:

I can still have weekly usage capacity available, but the 5-hour window can stop an active coding session anyway.

For users who work intensively on one or two days per week, this is much worse than a primarily weekly-based limit. A weekly allowance gives users the freedom to decide when to use their available capacity. The current system removes that flexibility.

For example, if I have several hours available on a weekend to work on a project, I want to use my weekly Codex allowance during that session. Being blocked by an additional short-term limit even though weekly capacity is still available feels unnecessarily restrictive.

In my view, one of these solutions would be significantly better:

• remove the 5-hour limit and keep the weekly limit,
• substantially increase the 5-hour allowance,
• make the weekly allowance the primary limit,
• or allow Plus users to choose between a short-term and weekly usage model.

I understand that OpenAI needs usage limits to manage capacity and costs. The issue is not that limits exist. The issue is how those limits are structured.

A weekly limit is predictable and flexible.

A weekly limit plus a restrictive 5-hour window can interrupt productive work even when the user still has unused weekly capacity.

For intensive Codex users, this makes the Plus plan noticeably less attractive.

I would be interested to know how many other Plus users prefer the weekly-only model or would like the 5-hour limit to be removed or significantly increased.

[luxd7]

SOL is a great model, but the five-hour window experience when you're using it is just terrible.

It feels like you're all excited to cook a big meal, and right when it's halfway done, the gas suddenly cuts out. You just have to stand there and watch the dish slowly cool down, and all your enthusiasm cools down right along with it.

After waiting five hours, sure, you can go back and finish cooking, but your mood is completely different by then. You'll never feel like that dish is a masterpiece anymore; you'll just be swearing at the gas company for ruining your whole day.

First, replacing the 5-hour limit with a weekly limit would provide a much better experience.

Second, if the allowance runs out before a task is finished, users should be completely allowed to keep going, with the extra usage simply debited from the next window.

Why not let the user finish cooking the meal and just bill them for the extra tab?

[robtroje-creator]

Feature request: Bankable 5-hour Codex reset credits
Allow users to occasionally earn or receive a credit that resets only their current 5-hour Codex usage window without resetting or increasing their weekly allowance.
The reset credit would not expire and could accumulate when Codex is not being heavily used.
For example, if I hit my 5-hour limit during an intensive development session, I could spend one reset credit and immediately begin a new 5-hour window. My normal weekly quota would remain unchanged.
There was previously a period where the 5-hour restriction was removed, and that experience was significantly better for development work. If removing the window entirely isn't practical, a bankable reset system would be a good compromise.
This would especially help developers whose usage is bursty: several hours of heavy work on one day followed by days of little or no Codex usage. The current rolling limit can interrupt productive sessions even though substantial weekly capacity may otherwise go unused.

[zj18610273107]

An abstract 5-hour design, Bengbu lived