[BUG] Plan upgraded but limit is not reset in sessions
Open 💬 20 comments Opened Feb 27, 2026 by dashidhy
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?
My Pro plan hits its limit, and I upgraded to Max immediately, which should extend the limit and let me continue working on my project, but Claude Code still shows "You've hit your limit" and asks me to wait for 3 hours for the reset. However, /usage shows the limit has already been reset, which is an inconsistent behavior.
What Should Happen?
Reset the limit immediately after the plan is upgraded.
Error Messages/Logs
Steps to Reproduce
Pro hits limit -> upgrade to Max -> back to Claude Code
Claude Model
None
Is this a regression?
I don't know
Last Working Version
_No response_
Claude Code Version
latest
Platform
Anthropic API
Operating System
macOS
Terminal/Shell
Terminal.app (macOS)
Additional Information
_No response_
20 Comments
Found 3 possible duplicate issues:
This issue will be automatically closed as a duplicate in 3 days.
🤖 Generated with Claude Code
I just ran into the same thing:
Seems like this must be an API bug.
Hi @milobird, it seems there is a bit of lag before the limit really resets; mine works after about 20 minutes. Hope this info helps you.
Hi, same problem here, hit the limit on pro plan, upgraded for the max x5 plan and still stuck on the limite. Do you find a solution ?
Edit: Updating the claude mac desktop seems to have fix the problem for me
Same problem here, @chimanos what do you mean by updating claude mac desktop? Did it actually infleunce your claude-code?
Same problem here. Hit 4-hour usage limit on max 5x plan with 2 hours left to reset time and started tapping in to my extra usage balance. Updated to max 20x usage plan but I am still stuck on using my extra usage balance. Reset time is unchanged.
Update: I went to the admin panel in the broswer (claude.ai/settings/usage) and toggled off the "Turn on extra usage to keep using Claude if you hit a limit" option. I then reopened claude code in my project and sent a message. That seemed to trigger a reset of the Current session balance.
thanks for the workaround - worked like a charm!
Another workaround is to delete your
~/.claudedirectory and then call claude again to re-authenticate.Generating a new session by calling
/login, and signing in again also seems to do the trick<b>This!!!</b>
I wiped my keychain completely, logged in, and still get this error. Tried the relogin and also the toggle switch fix. I cannot get this error to go away.
Only thing that works is to run CC as an agent weirdly, and even then it's not using 1M Context and I have to constantly compress
EDIT: I had to increase my usage limit even though I had extra money in the account it still locked me out until I did. I'll reduce it back next month
Grrr same problem!
same problem, and it used my extra usage and when i requested a refund the AI did not approve it
Same issue. I'm on a Team plan and hit my session limit so admin enabled extra usage and upgraded my seat. Claude Code still showed me as locked with Opus unavailable. /logout fixed it, but doing so cleared my entire active session and context.
worked.
Not working for me
Still happening:
-----
<img width="2115" height="253" alt="Image" src="https://github.com/user-attachments/assets/97bdbd34-15c2-4afb-afcf-3eae623560f8" />
-----
<img width="1780" height="875" alt="Image" src="https://github.com/user-attachments/assets/ea6ed595-cab7-4be0-a2dc-2df1efc356f9" />
This works, but it seemed to be initiated by uninstalling the desktop app and reinstalling (MacOS)
저도 같은 계열의 문제를 겪고 있습니다.
Pro에서 Max로 업그레이드했을 때, 기존 Pro 사용량이 Max의 더 큰 weekly limit 기준으로 즉시 재계산되는지, 아니면 기존 Pro usage/session state가 다음 rolling reset까지 유지되는지 명확하지 않습니다.
Anthropic Support에도 문의했지만, 공개 문서에는 이 전환 동작이 설명되어 있지 않고 지원 봇도 내부 동작을 확인하지 못했습니다. “Max는 즉시 적용된다”, “Claude와 Claude Code는 사용량 한도를 공유한다”는 일반 답변만 받았습니다.
이건 단순한 표시 문제가 아니라, Max 업그레이드 직후 실제 사용 가능량에 직접 영향을 주는 문제라고 생각합니다.