Allow unused Codex quota to roll over into a temporary bank

Open 💬 1 comment Opened Jun 12, 2026 by Jason-Wang313

What variant of Codex are you using?

CLI, but this is really an account-level usage feature that would benefit CLI, App, IDE Extension, and Web users.

What feature would you like to see?

Please allow unused normal Codex quota to roll over into a temporary bank instead of disappearing at the next automatic reset.

For example, if I have 50% of my Codex quota left and my normal reset happens tomorrow, I would like to save that unused 50% for later rather than losing it when the new cycle starts.

A safe version of this could be capped and time-limited, for example:

  • unused quota rolls into a temporary bank;
  • the bank is capped at 1 extra reset, or some fixed percentage such as 100% of one normal cycle;
  • banked quota expires after 7–30 days;
  • normal scheduled resets still happen as usual;
  • manually granted/banked reset tokens remain separate from unused quota rollover.

This would make Codex much more useful for users whose workload is bursty. Some days I do not need the full quota, while on other days I need a much heavier Codex session. Right now, unused quota before a normal reset feels wasted even when I know I will need it soon.

Additional information

I understand why unlimited rollover could be hard for capacity planning and abuse prevention. I am not asking for infinite quota hoarding. A small capped rollover would be enough.

Suggested behavior:

  • if a user has unused quota at reset time, move part of it into a temporary bank;
  • use current-cycle quota first;
  • use rolled-over quota only after current-cycle quota is exhausted;
  • clearly show the banked amount and expiration date in the usage UI;
  • make the feature work for CLI users too, even if the UI lives in the Codex app/web settings.

This would be especially helpful for Pro/Plus users who use Codex heavily but unevenly across days.

View original on GitHub ↗

This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗