codex - 💡(How to fix) Fix Usage limit reporting is inconsistent: session blocked while /status still shows % left [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openai/codex#19612Fetched 2026-04-26 05:13:55
View on GitHub
Comments
1
Participants
2
Timeline
5
Reactions
0
Timeline (top)
labeled ×3commented ×1unlabeled ×1

Root Cause

  • These two states are contradictory.
    • One part of the product says I am blocked because I exhausted usage.
    • Another part says I still have 62% of the 5-hour limit left.
    • This makes the limit reporting unreliable and prevents correct planning of work sessions.
RAW_BUFFERClick to expand / collapse

What version of the Codex App are you using (From “About Codex” dialog)?

v0.125.0

What subscription do you have?

Bussines

What platform is your computer?

Darwin 25.3.0 arm64 arm

What issue are you seeing?

I am reporting an inconsistency in Codex usage-limit reporting that makes the tool difficult to use reliably.

Actual behavior:

  • Codex shows a blocking message:
    • You've hit your usage limit. To get more access now, send a request to your admin or try again at 11:50 PM.
  • But /status at the same time reports:
    • 5h limit: 62% left
    • Context window: 60% left
    • Model: gpt-5.4 (reasoning medium, summaries auto)

Problem:

  • These two states are contradictory.
  • One part of the product says I am blocked because I exhausted usage.
  • Another part says I still have 62% of the 5-hour limit left.
  • This makes the limit reporting unreliable and prevents correct planning of work sessions.

Why this is a serious problem:

  • I cannot know whether I actually have remaining capacity.
  • The product becomes operationally unpredictable.
  • I may stop working unnecessarily, or waste time trying to continue when access is already blocked.
  • For long technical sessions, this is especially disruptive because the displayed budget cannot be trusted.

Expected behavior:

<img width="1568" height="619" alt="Image" src="https://github.com/user-attachments/assets/7b19a718-860f-4524-90ae-b4251652ce75" />
  • Screenshot attached showing:
    • blocking limit message at the top
    • /status showing 5h limit: 62% left

Claim:

  • The current reporting does not allow me to work correctly because it provides contradictory quota information.

What steps can reproduce the bug?

/status

What is the expected behavior?

No response

Additional information

No response

extent analysis

TL;DR

The inconsistency in Codex usage-limit reporting can be investigated by checking the calculation and synchronization of usage limits between different components of the Codex App.

Guidance

  • Verify the usage limit calculation logic to ensure it accurately reflects the remaining capacity.
  • Check the synchronization mechanism between the blocking message and the /status endpoint to ensure they are using the same data source.
  • Investigate potential caching or latency issues that could cause the discrepancy between the two reports.
  • Review the documentation or support resources for the Codex App to see if there are any known issues or workarounds related to usage limit reporting.

Notes

The issue seems to be related to a discrepancy between different components of the Codex App, and resolving it may require changes to the app's internal logic or synchronization mechanisms.

Recommendation

Apply workaround: Until the issue is resolved, users can try to use the /status endpoint as a more reliable indicator of their remaining usage limit, but be aware that the blocking message may still appear even if the limit is not actually exceeded.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

codex - 💡(How to fix) Fix Usage limit reporting is inconsistent: session blocked while /status still shows % left [1 comments, 2 participants]