Drop the 5-hour window for Plus subscribers — keep the weekly cap
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 125k
- Forks
- 19.4k
- PR merge metrics
- PR metrics pending
Description
Drop the 5-hour window for Plus subscribers — keep the weekly cap
Plus subscribers have a weekly Codex allowance and a 5-hour rolling window on top of it. Pro subscribers only have the weekly cap. The 5-hour window was removed for everyone during the GPT-5.6 rollout in July (announced by Tibo Sottiaux, July 12), then brought back for Plus in late August.
If the weekly cap is enough to manage load from Pro users, the 5-hour window on Plus is a tier gate, not an infrastructure safeguard.
What the window does in practice: I hit the limit mid-task, wait hours, come back, spend tokens re-establishing context, and burn more of my weekly allowance than finishing in one sitting would have cost. The limit makes the same usage cost more tokens because I lose context and have to rebuild it.
#34035 collected 150+ reactions during the period the window was removed. Users preferred the weekly-only model. It came back anyway, but only for the lower-paying tier.
Asking for:
- Remove the 5-hour window for Plus, matching the Pro experience
- Weekly cap stays as the single constraint across both tiers
- If demand spikes need a temporary throttle, apply it transparently across tiers instead of baking it into one plan permanently
I don't want more usage. I want to pick when I spend what's already included in my plan.
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
No files, tests, or entry points are identified. Start by locating where Plus and Pro allowance limits are enforced, then review issue #34035 for the prior weekly-only behavior. Done means Plus no longer has a 5-hour rolling window, both tiers retain the weekly cap, and any temporary throttling is applied transparently across tiers.
Written by the indexing model from the issue text.
Assessment
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100