[BUG]

Preflight Checklist

• [x] I have searched existing issues and this hasn't been reported yet
• [x] This is a single bug report (please file separate reports for different bugs)
• [x] I am using the latest version of Claude Code

What's Wrong?

Bug Report — Usage Limit Enforced Despite 0% Session Usage Shown
Plan: Claude Max 20x ($200/month)
Issue: The system is displaying "Usage limit reached" with a future reset time, while simultaneously showing 0% of the current 5-hour session used. These two states are mutually exclusive and cannot both be accurate. The enforcement is blocking access, but the usage meter shows no consumption has occurred.
Expected behavior: If the session meter shows 0% used, no usage limit should be triggered.
Actual behavior: Access is blocked with a "Usage limit reached" banner and a reset timer, despite the session usage meter reading 0%. The enforcement system and the usage display are completely out of sync.
Additional context: In order to work around the block and submit this bug report, I was forced to purchase additional usage credits — despite being on the Max 20x plan and having consumed 0% of my session. This is a direct financial impact caused by the bug. This issue is consistent with multiple confirmed reports on Anthropic's own GitHub (issues #62125, #54177, #61828) describing the same desync between limit enforcement and displayed usage meters.

What Should Happen?

Request: A root cause explanation, a fix, and a refund of any usage credits spent as a direct result of this enforcement error.

Error Messages/Logs

Steps to Reproduce

I guess you'd have to hit your usage limit, upgrade to Claude Max 200, watch your usage limit in your settings go to zero, and yet on your chat it would still say you've reached your usage limit.

Claude Model

Opus

Is this a regression?

I don't know

Last Working Version

_No response_

Claude Code Version

1.21459.3.0

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

Windows Terminal

Additional Information

Well, I also spent eight and a half hours trying to debug the MCP server, but that's yet another bug. What's funny is I went over my usage limit trying to debug the MCP server. I didn't even get to work on my own projects.