claude-code - 💡(How to fix) Fix Weekly usage shows 0% after Max x20 upgrade but chats remain blocked [2 comments, 2 participants]

Summary

After upgrading my plan from Max x5 to Max x20, my weekly usage indicator now correctly shows 0% used (previously 100% / rate-limited on the x5 plan). However, Claude Code chats remain blocked as if I am still over the limit. The two states are inconsistent — either the UI is reporting the wrong remaining quota, or the session/rate-limit handling is not picking up the new plan tier.

To unblock myself and file this report I had to enable "extra usage" (pay-as-you-go overage), which itself confirms the chats are still being treated as rate-limited despite the 0% display.

Expected behavior

After a plan upgrade that resets/expands weekly quota:

• The usage UI and the rate-limit gate should agree.
• If the UI shows 0% used on the new tier, chats should be allowed on that tier's quota without needing to toggle extra usage.

Actual behavior

• Usage UI: 0% used (post-upgrade, Max x20).
• Chat behavior: blocked as if still rate-limited; only unblocked by enabling extra usage.

Reproduction

1. Hit weekly usage cap on Max x5 (UI shows 100% used, chats blocked).
2. Upgrade to Max x20.
3. Observe usage UI updates to 0% used.
4. Attempt to start a chat in Claude Code → still blocked.
5. Enable extra/overage usage → chats work again.

Likely root cause

One of:

• UI is reading the new entitlement but the rate-limit decision is keyed off a cached pre-upgrade quota/window state.
• Session-side rate-limit token wasn't refreshed after the entitlement change.
• The weekly-window counter wasn't reset/rescaled when the plan tier changed mid-window.

Environment

• Plan: upgraded from Max x5 → Max x20 (just now)
• Workaround: extra usage toggled on