›_ Codex Issues
Codex Issues / #2009

Rate-limit banner typo + opaque limits

Resolved 💬 2 comments Opened Aug 8, 2025 by zemaj Closed Oct 17, 2025

What version of Codex is running?

codex-cli 0.19.0

Which model were you using?

gpt-5

What platform is your computer?

Darwin 24.5.0 arm64 arm

What steps can reproduce the bug?

  1. Open codex CLI using an OpenAI Plus/Pro account.
  2. Run normal workflows for ~1–2 hours (light coding/planning is enough) until rate limits are hit.
  3. Observe the banner that appears when the cap is reached.

What is the expected behavior?

  • Correct grammar in the banner.
  • Transparent limits displayed at the moment of failure and queryable at any time:

Remaining vs. total requests/runs, tokens (if applicable), and per-model breakdown.
Time-to-reset for the rolling 5-hour window and the weekly window (absolute timestamps).

  • Early warnings at ~80% and ~95% of the cap with actionable guidance (e.g., suggest lowering reasoning effort or switching models).
  • A command (e.g., codex usage) that shows the same counters on demand.

What do you see instead?

  • Banner text shows a typo/grammar error:
🖐 You've hit usage your usage limit. Limits reset every 5h and every week.
  • No counters, no per-model breakdown, and no time-to-reset.
  • No early warning before the hard stop.
  • No obvious command to check current usage status.

Additional information

Users cannot plan work, adapt settings, or switch models before hitting a hard stop.

View original on GitHub ↗

2 Comments

takemiyamakoto · 1 year ago

Yeah, it is pretty unusable at the moment. I am not running a thousand instances, just trying to fix a couple of compile errors, so it would be nice to be able to keep it running to fix my backlog while I do other stuff, but it doesn't work if I have to context switch every hour or so. I'm a pro user, so it would be nice to have pro tier be able to do work all day long without having to stop.

bharadwaj-pendyala · 5 months ago

+1. The missing piece for me is a reliable command-level view of Codex usage before the limit is hit. I often use Codex through multiple surfaces like the CLI and UI, and they appear to draw from the same quota pool. Without a built-in usage command, it is easy to get interrupted in the middle of long refactors, repo-wide analysis, or multi-step coding sessions with no warning. A command like codex usage or codex status --limits that shows current plan, used quota, remaining quota, and reset time would make Codex much easier to plan around.