Severe reduction in effective Codex usage since the return of 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 version of the Codex App are you using (From “About Codex” dialog)?
26.810.52044
What subscription do you have?
Plus
What platform is your computer?
Darwin 25.5.0 arm64 arm
What issue are you seeing?
Severe reduction in effective Codex usage since the return of the 5-hour limit
The issue isn't only that the 5-hour window has returned. The amount of actual work I can perform within that window appears to have dropped dramatically compared with previous weeks.
With essentially the same workflow and similar tasks, my quota is now consumed several times faster.
This effectively represents a substantial reduction in the usable Codex allowance of my subscription.
Please clarify whether the metering algorithm, token weighting, model costs, or the 5-hour quota allocation has recently changed.
What steps can reproduce the bug?
About a week ago, I was able to get roughly 5 times more actual work done with the same percentage of my 5-hour Codex usage limit.
My workflow, project size, and type of tasks have not changed significantly, but the 5-hour quota is now being consumed dramatically faster.
This is not a small difference: the effective amount of work I can perform before hitting the limit appears to have dropped by around 80% compared with a week ago.
To reproduce it, use Codex on a normal existing codebase with regular coding/refactoring tasks and compare the percentage of the 5-hour quota consumed with the same type of workload from approximately one week ago.
What is the expected behavior?
No response
Additional information
No response
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
Start by reviewing the Codex App version, subscription, platform, and the reported five-hour quota behavior. Compare the same workflow and workload against the earlier period described in the issue; done means determining whether the observed consumption change is reproducible and identifying whether metering, model costs, or quota allocation changed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100