Allow weekly quota to extend Codex 5-hour usage window

What version of Codex CLI is running?

codex-cli 0.150.1

What subscription do you have?

ChatGPT Plus

Which model were you using?

gpt-5.6-sol

What platform is your computer?

No response

What terminal emulator and version are you using (if applicable)?

No response

Codex doctor report

What issue are you seeing?

This is a product/usage-policy feedback request rather than a CLI bug.

The rolling 5-hour Codex usage limit can block a long development session even when substantial weekly quota is still available.

I use Codex CLI for long, continuous development sessions involving large codebase analysis, implementation, debugging, iterative review, Linux kernel development, and large-scale refactoring.

Some tasks need to be completed in one continuous session, so there are cases where I intentionally need to consume a large portion of my weekly quota in a single day.

However, the 5-hour limit prevents this even though weekly quota remains.

I am not requesting any increase to the total weekly quota.

My preferred policy change is:

After the 5-hour window is exhausted, allow users to continue using Codex as long as weekly quota remains, deducting that additional usage from the remaining weekly quota.

For example:

5-hour quota: exhausted
Weekly quota: 60% remaining

→ Allow continued usage while consuming the weekly quota faster.

A "burst mode" or "spend weekly quota to extend the 5-hour window" option would solve this problem while keeping the same total weekly usage allowance.

This would allow developers to decide when to consume the weekly quota already included in their subscription.

Codex feedback thread ID:
01a04cc7-48dd-74a1-b08a-46945204c2ec

What steps can reproduce the bug?

Uploaded thread: 01a04cc7-48dd-74a1-b08a-46945204c2ec

What is the expected behavior?

If weekly Codex quota still remains, users should be able to continue working after the 5-hour window is exhausted.

The additional usage could simply consume the remaining weekly quota faster.

For example:

5-hour quota: exhausted
Weekly quota: 60% remaining

→ Allow continued Codex usage while deducting the additional usage from the weekly quota.

A "burst mode" or "spend weekly quota to extend the 5-hour window" option would be an ideal solution.

I am not requesting an increase in the total weekly quota.

Additional information

This limitation is especially disruptive for long, uninterrupted software development sessions such as:

• large codebase analysis
• Linux kernel development
• debugging
• large-scale refactoring
• agent-driven implementation
• iterative test/review cycles

Some development tasks need to be completed in a single continuous session, so I may intentionally want to consume a large portion of my weekly allowance in one day.

The current 5-hour rolling limit prevents that even when substantial weekly quota remains.

My request is only for more flexibility in when the existing weekly quota can be consumed, not for additional total weekly usage.

Codex feedback thread ID:
01a04cc7-48dd-74a1-b08a-46945204c2ec

Start by reviewing the requested policy change and the linked Codex feedback thread 01a04cc7-48dd-74a1-b08a-46945204c2ec; this issue names no source files, tests, or implementation entry point. Done would mean defining and implementing a supported burst mode that can consume remaining weekly quota after the rolling five-hour limit is exhausted, without increasing total weekly allowance.