Feature Request: Replace Weekly Usage Limits with Daily Rolling Caps for Codex

ChatGPT Feature requests
,
1

Proposal Summary

Transition Codex usage limits from multi-day/weekly quota blocks to predictable daily rolling limits.

Problem

During heavy development sessions (such as deep debugging, full repository refactoring, or agentic task loops), developers can easily exhaust an entire weekly Codex allowance in 1–2 days. This results in complete lockouts from primary models for up to 6 consecutive days, completely stalling development workflows.

Proposed Solution

  1. Daily Rolling Caps: Convert usage allowances into 24-hour rolling windows (e.g., a dedicated daily request/token budget).
  2. Burst Buffer / Rollover: Allow a small percentage of unused daily quota to carry over into a secondary buffer to accommodate heavy release or refactoring days.
  3. Predictable Pacing: A daily reset schedule gives developers a clear, manageable budgeting routine without multi-day lockouts mid-project.

Benefits

  • Uninterrupted Workflow: Prevents multi-day project blockages during critical dev cycles.
  • Fair Compute Distribution: Keeps server load balanced daily while providing developers predictable access.
2

Hey djgcarney97, welcome to the forum!

Thanks for bringing this up. The proposal is feasible, and a daily-only replacement could make Codex less useful for developers who work in concentrated sessions. A stronger design would preserve a larger weekly pool while adding clearer pacing information, a guaranteed daily minimum, or optional user-controlled allocation.

However, I will surface this to product team who will look into this and see if it can be implemented.

Avinash