`Adjust the 5‑hour usage limit for ChatGPT Plus Codex to support sustained developer workflows` >

What variant of Codex are you using?

App/Web

What feature would you like to see?

Feedback on the Codex 5-Hour Limit for Plus Users

I think the current 5-hour Codex usage limit on ChatGPT Plus is too restrictive for developers who use Codex as part of their primary development workflow.

The main issue is not simply the amount of usage available. The 5-hour window itself does not align well with how developers actually work.

Most developers do not work 24 hours a day or distribute their Codex usage evenly throughout the day. In practice, productive development time is usually concentrated within an 8–10 hour working period.

For example, my typical workflow is:

Write requirements → let Codex read and understand a large codebase → modify multiple files → run tests → analyze failures → make additional changes → run tests again.

Codex is involved throughout most of my development process.

With this type of workflow, it is possible to hit the 5-hour limit while still having a significant amount of weekly usage remaining. This interrupts an active development session and forces the developer to wait for the usage window to reset.

Meanwhile, resets that occur during sleep or other non-working hours provide little practical value. As a result, the amount of Codex usage that a developer can realistically utilize during a normal working day can be significantly lower than the theoretical allowance available across 24 hours.

I think a better system could be one of the following:

1. Increase the 5-hour allowance for Plus users.
2. Make the 5-hour limit primarily a safeguard against extreme short-term usage, while allowing the weekly limit to be the main usage constraint.
3. Replace the current system with a daily + weekly allowance, allowing developers to decide how to use their daily capacity during their working hours.
4. Introduce separate 5-hour reset and weekly reset options, potentially including purchasable resets.

The weekly limit already provides a mechanism for controlling overall usage. A very restrictive 5-hour limit on top of it can unnecessarily interrupt legitimate, sustained development workflows.

For developers who use Codex heavily for reading large repositories, implementing features, refactoring code, running tests, debugging, and iterating autonomously, uninterrupted working time is extremely important.

I hope OpenAI will consider adjusting the 5-hour limit for Plus users so that Codex better supports sustained, real-world software development workflows.

Additional information

_No response_