Show global usage and reset time for 5h/weekly guardrails in Codex CLI

Resolved 💬 6 comments Opened Aug 8, 2025 by agenticbuddy Closed Oct 19, 2025
💡 Likely answer: A maintainer (tibo-openai, collaborator) responded on this thread — see the highlighted reply below.

Feature request:
When usage limits are enforced (e.g., 5-hour or weekly guardrails), it would be extremely helpful if Codex CLI could display:

  1. Global usage within the current window (not just the current session):
  • Total tokens / requests used in the active 5h or weekly window.
  • How much of the allowance remains.
  1. Reset information:
  • Exact time when the current window will reset (e.g., "Resets in 2h 15m").
  • If multiple windows apply (e.g., 5h and weekly), show both.
  1. Effective plan and limiter context:
  • The plan currently applied on the backend (e.g., Pro or Plus), even if different from the local token’s plan.
  • The type of guardrail or limiter that triggered (rate limit, reasoning window, etc.).

This would make it clear to the user:

  • Whether the limit is session-based or global.
  • How close they are to hitting the limit.
  • How long they need to wait before being unblocked.

It would also help identify plan upgrade propagation issues, such as continuing to enforce Plus-level guardrails after upgrading to Pro.

View original on GitHub ↗

6 Comments

AlexJanow · 1 year ago

Any updates on this?

ZackHirshhorn · 1 year ago

Would also like to know. It can limit usage time to less than 3 hours, that's a deal-breaker.

bernaferrari · 11 months ago

Claude added a "status-bar" like where anyone can use any plugins or extensions to customize it the way you want. The most popular one is context. Maybe something similar for Codex could make sense, expose the context via an API and allow user to tweak the status bar below the input.

<img width="382" height="95" alt="Image" src="https://github.com/user-attachments/assets/365a3fab-3d8e-459a-a596-b3da3375249b" />

tibo-openai collaborator · 10 months ago

We now have 1, 2 and parts of 3 under /status. The amount of context used is also displayed under the composer. Thanks a lot for the detailed feature request, will close this, but please open new ones for other features you would like to see added or improved.

mike-red-shift · 6 months ago

We've got a business account with OpenAI and this degree of instability is not acceptable. OP's suggestions are the BARE minimum.

anowardear062-svg · 6 months ago

Support and proses