/status shows 83% of weekly limit left, but every prompt is blocked with "You've hit your usage limit. Upgrade to Plus" (already on Plus) #32680

Title: /status reports 83% of weekly limit remaining, but every prompt is blocked with "You've hit your usage limit. Upgrade to Plus" (already on Plus)

Summary

On a Plus ChatGPT account, Codex's account/entitlement state appears to get out of sync mid-session. A working agent session suddenly started returning HTTP 400, /status intermittently showed the account as Free (it is not), and after re-login it correctly showed Plus but now blocks every prompt with a "usage limit" error — even though /status reports 83% left of the weekly limit. The error asks me to upgrade to Plus, which I already have, and its reset date disagrees with the one shown in /status. Reinstalling Codex did not help.

Timeline

1. Was using an agent session normally on model gpt-5.6-sol — everything worked, wrote a fair amount of code.
2. Mid-session, requests suddenly began failing with HTTP 400 (The 'gpt-5.6-sol' model is not supported when using Codex with a ChatGPT account.).
3. At that point /status showed the account as Free, which is incorrect — it is a paid Plus account that had been working moments earlier.
4. Logged out and back in. /status then correctly showed Plus.
5. But now every prompt is rejected with "You've hit your usage limit. Upgrade to Plus…", while /status simultaneously reports 83% left.
6. Reinstalling Codex (brew reinstall --cask codex) did not resolve it.

Environment

• Codex version: v0.144.1 (codex-cli 0.144.1)
• Install method: Homebrew cask (brew install --cask codex)
• OS: macOS (Apple Silicon / arm64)
• Account tier: Plus
• Model: gpt-5.6-terra (reasoning high, summaries auto)
• Permissions: Workspace (Approve for me)

Steps to reproduce

1. Launch codex on a Plus account.
2. Run /status.
3. Send any prompt (e.g. Test).

What /status shows

Model:          gpt-5.6-terra (reasoning high, summaries auto)
Permissions:    Workspace (Approve for me)
Account:        <redacted> (Plus)
Weekly limit:   [#################...] 83% left (resets 06:20 on 20 Jul)

Actual behavior

Any prompt is immediately rejected:

You've hit your usage limit. Upgrade to Plus to continue using Codex,
or try again at Aug 7th, 2026 12:39 AM.

Expected behavior

With 83% of the weekly limit remaining on a Plus account, prompts should be accepted. If the account is genuinely rate-limited, /status should reflect that (0% left) rather than reporting 83% remaining.

Inconsistencies observed

1. Limit state disagrees with /status. /status says 83% left, but the request path reports the limit as fully hit.
2. Reset dates disagree. /status says the weekly limit resets 06:20 on 20 Jul; the error says to try again Aug 7th, 2026 12:39 AM.
3. Wrong upsell. The error tells an existing Plus subscriber to "Upgrade to Plus."

gpt-5.6-sol 400 (likely the same root cause)

The gpt-5.6-sol model was working in the same session and then started returning HTTP 400 mid-session:

{"type":"error","status":400,"error":{"type":"invalid_request_error",
"message":"The 'gpt-5.6-sol' model is not supported when using Codex with a ChatGPT account."}}

The message ("not supported when using Codex with a ChatGPT account") lines up with /status showing the account as Free at that same moment — i.e. it looks like the client's view of the account entitlement flipped mid-session, which broke both the model and the usage-limit accounting. If this model genuinely isn't supported for ChatGPT-account auth, it also should not remain selectable / should surface a clearer message before sending the request.