openai / openai/codex

Usage limit reset does not clear 5-hour rolling window

Open
#43,892 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug codex-web rate-limits
Dominant language
Rust
Stars
125k
Forks
19.4k
PR merge metrics
PR metrics pending

Description

Description

After using a "Full reset" from the Codex usage settings page (https://chatgpt.com/codex/settings/usage), the weekly limit resets to 100% but the 5-hour rolling window is not cleared. Codex continues to return:

ERROR: You've hit your usage limit. ... try again at 7:58 PM.

This happens for both codex exec and TUI mode. The "remote compact task" (used during codex exec fork) also fails with the same rate limit error.

Steps to reproduce

  1. Use Codex until the 5-hour rolling limit is hit
  2. Go to https://chatgpt.com/codex/settings/usage
  3. Click "Use Reset" (Full reset)
  4. Weekly limit shows 100% remaining
  5. Run any codex command — still rate limited with the original "try again at" time

Expected behavior

The reset should clear both the weekly limit AND the 5-hour rolling window, as documented in https://help.openai.com/en/articles/20001498-how-banked-codex-resets-work

Environment

  • Codex CLI v0.153.4
  • Auth mode: ChatGPT (not API key)
  • Platform: Linux x86_64 (Ubuntu 24.04)

Related issues

#31532, #31575, #32107, #32311, #34865

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

Start by reproducing the reset flow from the Codex usage settings page with codex exec and TUI mode after the 5-hour limit is reached. Check how the CLI handles the usage-limit response, including the remote compact task used by codex exec fork, and compare behavior before and after a Full reset. Done means the weekly and 5-hour limits are both cleared and the commands no longer report the old retry time.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
cli
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.