[BUG] "Current session" hitting 100% didn't trigger a stop/warning
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?
I had a Claude Code CLI session going using Fable. I have a Claude Team account for work and my Curent Sesssion Limit of 100% was reached but the session did not stop and I was not prompted. This accrued $71.86 in charges.
I feel this should be credited as I was not prompted and not stopped (which is what I would have expected when additional overage charges are involved). I have seen this prompt in the past.
What Should Happen?
Further API calls should be blocked with a prompt until confirmation from the user to proceed knowingly exceeding session limits.
Error Messages/Logs
Steps to Reproduce
I can't reproduce but I had a CLI session using Fable involving the superpowers plugin and it was working through the design and planning phases when the current session limit hits 100%.
Claude Model
_No response_
Is this a regression?
Yes, this worked in a previous version
Last Working Version
_No response_
Claude Code Version
2.1.202
Platform
Anthropic API
Operating System
macOS
Terminal/Shell
Warp
Additional Information
_No response_