openai / openai/codex

Remove the 5-hour usage window for Extra High / Max / Ultra reasoning modes

Open
#41,160 2 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

app enhancement rate-limits
Dominant language
Rust
Stars
125k
Forks
19.4k
PR merge metrics
PR metrics pending

Description

What variant of Codex are you using?

App

What feature would you like to see?

For long-running Codex tasks, the 5-hour usage window becomes a major limitation when using GPT-5.6 Sol or Daybreak Blue at higher reasoning levels such as Extra High, Max, and Ultra.

In intensive agent workflows, the entire 5-hour allowance can sometimes be exhausted in only 15-25 minutes of actual work. A single deep research task then has to be interrupted and resumed across 3-4 separate 5-hour windows.

The problem is not only the delay. After a multi-hour interruption, Codex can recover persisted context, but it often loses some of the exploratory momentum of the previous run: it tends to reconstruct the task, close the currently visible branch, and move toward summarization instead of continuing the same deep search trajectory. This can materially reduce the quality of long-running research, debugging, security analysis, and other exploratory agent tasks.

I suggest that Extra High / Max / Ultra should not be constrained by the 5-hour usage window at all. Instead, keep the overall weekly allowance and let users consume that allowance continuously when needed.

The total amount of compute available to the user would not have to increase - this would simply remove the artificial 5-hour fragmentation.

In other words:

Current: weekly quota + 5-hour sub-limit → one deep task is repeatedly interrupted.

Suggested: weekly quota only for Extra High / Max / Ultra → the same quota can be spent continuously on one task.

This would make the highest reasoning modes substantially more useful for the kinds of long-running tasks they are best suited for.

Additional information

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue concerns App usage limits for Extra High, Max, and Ultra reasoning modes, but it names no files, tests, or entry points. Start by locating where the 5-hour and weekly quotas are defined, then determine whether removing only the sub-limit preserves the weekly allowance while allowing one task to continue uninterrupted.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
ai
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.