Make the 5-hour Codex limit dynamic based on available infrastructure capacity

What variant of Codex are you using?

App

What feature would you like to see?

Problem

The current fixed 5-hour Codex limit can block users for several hours even when they still have 70–80% of their weekly allowance available.

I understand the purpose of the 5-hour window: preventing extreme burst usage and helping OpenAI smooth infrastructure demand. The problem is that a fixed short-term limit does not account for actual system capacity.

Proposal

Keep the weekly allowance unchanged, but make the 5-hour burst allowance dynamic based on available infrastructure capacity.

For example:

During high-load periods, the 5-hour bucket might allow only ~8–12% of the weekly allowance.
During normal load, ~15–20%.
During low-load periods, ~25–30% or more.

The UI could show the current available burst capacity, for example:

Current 5-hour capacity: 27% of weekly allowance

This would encourage power users to move heavy workloads toward periods when OpenAI has spare capacity, while still protecting infrastructure during peak demand.

Why this would be better

It would not increase the user's total weekly entitlement. It would only make that allowance more flexible to consume when capacity is available.

Today, a user can have most of their weekly allowance remaining but still be completely unable to continue working for several hours. A dynamic burst limit could reduce that frustration while potentially improving infrastructure utilization at the same time.

An optional alternative would be a continuously replenishing token-bucket system rather than a hard 5-hour reset.

Additional information

I use Codex in concentrated development sessions rather than evenly throughout the week, so the current fixed window often becomes the limiting factor long before my weekly allowance does.

No files, tests, or entry points are identified. Start by locating where the App enforces the fixed 5-hour and weekly allowances; done would require an agreed capacity-based allowance, preserved weekly entitlement, and the proposed capacity information exposed in the UI.