usage limit codex app bug

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

v0.130.0

What subscription do you have?

PLUS

What platform is your computer?

ubuntu

What issue are you seeing?

Codex CLI reports usage limit hit while /status and web usage page show remaining allowance

Hi,

I am seeing an inconsistency between the Codex CLI usage-limit error and the actual usage shown in both the CLI /status command and the Codex web usage page.

Problem

Codex CLI refuses to process new prompts and shows:

You've hit your usage limit. Upgrade to Pro (https://chatgpt.com/explore/pro), visit https://chatgpt.com/codex/settings/usage to purchase more credits or try again at 6:44 PM.

However, /status shows that I still have plenty of usage remaining:

OpenAI Codex v0.130.0

Model: gpt-5.4 (reasoning medium, summaries auto)
Account: [redacted] (Plus)

5h limit:      89% left (resets 18:44)
Weekly limit:  82% left (resets 16:21 on 19 May)

The web usage page also shows:

5 hour usage limit: 89% remaining
Weekly usage limit: 82% remaining

What I tried

I logged out and logged back in:

codex logout
codex login

After logging in again, the issue still happens.

I also checked /status again after re-login, and it still shows that I have remaining allowance.

Expected behavior

If /status and the web usage page show remaining usage, Codex CLI should allow me to continue using the model.

Or, if there is another limit being hit, the CLI should show that specific limit clearly.

Actual behavior

Codex CLI blocks all prompts with a usage-limit error, even though both /status and the web usage page show available remaining usage.

Environment

OpenAI Codex v0.130.0
Plan: ChatGPT Plus
Model: gpt-5.4
Reasoning: medium
Summaries: auto

Notes

This looks like either:

• a hidden short-term/burst rate limit not reflected in /status,
• a model-specific limit not shown in the usage UI,
• stale/incorrect usage state between the CLI and backend,
• or a bug in how Codex CLI interprets the current usage state.

Thanks.

<img width="1477" height="224" alt="Image" src="https://github.com/user-attachments/assets/ecfdcd40-3c43-44b0-9f10-e4e8c244a0f9" />

<img width="1347" height="271" alt="Image" src="https://github.com/user-attachments/assets/54dc3e0c-7739-497d-98f4-501021ea9cbd" />

What steps can reproduce the bug?

i have no idea,

What is the expected behavior?

_No response_

Additional information

_No response_