False "over 90% of your weekly limit" warning even when /status shows ~96% left #7464

What version of Codex is running?

OpenAI Codex CLI v0.63.0

What subscription do you have?

ChatGPT Plus

Which model were you using?

gpt-5.1-codex-max

What platform is your computer?

macOS 26.1 (25B78) (ARM)

What issue are you seeing?

The Codex CLI shows a yellow banner that says:

"Heads up, you've used over 90% of your weekly limit. Run /status for a breakdown."

However, when I run /status, the detailed usage numbers clearly contradict this warning. For example, /status shows something like:

• Context window: 100% left (10.9K used / 272K)
• 5h limit: 87% left
• Weekly limit: 96% left

So the banner claims I’ve used over 90% of my weekly limit while /status reports that I still have ~96% of the weekly limit left. It looks like the banner is using different or stale data, or the threshold logic is incorrect.

Screenshots attached with personal info redacted.

What steps can reproduce the bug?

1. Start the Codex CLI.

2. Use the model gpt-5.1-codex-max in a normal session.

3. After a small amount of usage, the yellow banner appears at the top:

   "Heads up, you've used over 90% of your weekly limit. Run /status for a breakdown."

4. Inside the same session, run /status.

5. Observe that the /status output shows high remaining usage (e.g., Weekly limit: 96% left), which contradicts the banner message.

Uploaded thread: 019adbd5-c8aa-7080-9a48-6ae77ed4a87c

What is the expected behavior?

The yellow "over 90% of your weekly limit" warning should only appear when the actual weekly usage is above 90% (or when the remaining weekly limit is low).

If /status shows that I still have around 96% of my weekly limit left, the warning should not be shown. The banner and the /status breakdown should be consistent and based on the same data.

Additional information

• Account type: ChatGPT Plus.
• This happened even though this is very early in the week and I have barely used the CLI.
• The problem appears to be purely cosmetic (a UI/logic bug in the warning), since the actual limits shown by /status look correct.