Allow weekly-only Codex usage without the 5-hour limit
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 125k
- Forks
- 19.4k
- PR merge metrics
- PR metrics pending
Description
What variant of Codex are you using?
App, CLI
What feature would you like to see?
The temporary removal of the 5-hour Codex usage limit was one of the biggest improvements to Codex for our workflow.
We are a business customer and use Codex heavily for professional development work. We currently operate multiple Codex accounts and significantly expanded our Codex usage after the 5-hour restriction was removed.
The weekly usage limit itself is not the problem.
The problem is the additional 5-hour window.
For professional development work, usage is rarely distributed evenly throughout the week. On some days we may work intensively with Codex for many hours, while on other days we barely use it.
With a weekly-only quota, we were able to decide ourselves when to consume the usage we already paid for.
The reintroduction of the 5-hour limit removes that flexibility and creates essentially the same problem we already experience with competing coding assistants.
At the moment, several of our accounts still have almost the entire weekly quota available, but an additional short-term limit can prevent us from continuing productive work.
We are not asking for a larger weekly quota.
We are asking for the ability to use the existing weekly quota more flexibly.
Suggested solution
Please consider one of the following:
Remove the 5-hour usage limit again and keep only the weekly limit.
Allow users to choose between:
Protected usage: 5-hour + weekly limit
Flexible usage: weekly limit only
This would protect users who do not want to accidentally consume their entire weekly quota quickly, while allowing professional and power users to manage their own usage.
The weekly-only model was a major reason why we increased our Codex usage and invested in additional accounts.
Please consider bringing this flexibility back.
Additional information
We expanded our Codex usage and added multiple paid accounts specifically after the 5-hour restriction was removed, because the weekly-only model worked significantly better for our development workflow. The return of the 5-hour window directly changes the value proposition for us and may affect whether we continue expanding our Codex usage. We would strongly prefer to remain with Codex, but the weekly-only usage model was a major reason for choosing it over competing coding assistants.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names Codex App and CLI usage limits but provides no files, tests, or entry points. Start by locating where the 5-hour and weekly quota policies are defined; done would mean supporting weekly-only usage or a user-selectable protected versus flexible mode without increasing the weekly quota.
Written by the indexing model from the issue text.
Assessment
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100