Usage limits UI shows available 5-hour quota when weekly limit is exhausted

Open 💬 1 comment Opened Jul 6, 2026 by Yuxin-Qiao

Summary

When the weekly usage limit is fully exhausted (0% remaining), the Codex usage UI can still show the 5-hour limit as nearly full (e.g. 99% remaining) with an imminent reset time. That is misleading because the product is unusable until the weekly window resets.

Steps to reproduce

  1. Use a Codex Plus account until the weekly limit is exhausted (0% remaining).
  2. Open Codex usage / account limits (profile menu → usage limits, or equivalent).
  3. Observe the 5-hour and weekly rows.

Expected behavior

When the weekly cap is the binding limit, the 5-hour row should reflect that session quota is not usable until the weekly reset — e.g. show 0% remaining, be visually disabled, or hide the misleading 5-hour reset countdown.

Actual behavior

  • Weekly: 0% remaining, reset on the correct weekly date.
  • 5-hour: still shows ~99% remaining with a near-term reset time (e.g. 16:59).
  • Main Codex UI correctly blocks usage with “message limit exhausted” and points to the weekly reset.

Screenshot

!Weekly exhausted but 5-hour still shows 99%

Context

Third-party usage monitors (e.g. CodexBar) already treat weekly exhaustion as a global cap over the 5-hour bucket because the rate-limit API returns per-window numbers independently. The official limits UI appears to surface those windows without the same binding-cap semantics.

Environment

  • Plan: Codex Plus (Apple subscription)
  • Platform: macOS Codex app / chatgpt.com Codex
  • Date observed: 2026-07-06

View original on GitHub ↗

This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗