[BUG] Session limit reached far ahead of time compared to entire month of March.

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 have been chewing through tokens much faster in the last few days compared to the entire month of March. I am on Max x5 for a month now, and the last few sessions were exhausted in very little time, some of them only 30-60 minutes in. I haven't changed anything in the way I work. I am a hobbyist but am using CC a lot, basically every day for many hours, and I have exhausted my 5-hour limit for the first time on the x5 plan within the last 24-36 hours. Claude have written and edited tens of thousands of lines of code for me and have never so far came to this limit. I have been monitoring the usage bar closely every day, I never noticed it as bad as it is these days. Literally 1 prompt can cost me 15-18% of the 5hr limit - and no, it's not a giant ask, simply asking it to fill in content for a website template I already have, for example. Everything exists, it doesnt need to rebuild anything, just fill in content. The prompts I've been giving are token-eco by design.
Hope this get sorted soon. Thanks for all the hard work you've been putting in. Cheers!

What Should Happen?

I am not a very heavy user but I am building stuff with CC, I shouldn't reach the limit this fast. When I did hit it - I upgraded to x5, and for weeks haven't come close to the 5-hr session limit on very intense sessions where Claude literally wrote thousands of lines of code in a single session.

Error Messages/Logs

Steps to Reproduce

n/a

Claude Model

Opus

Is this a regression?

Yes, this worked in a previous version

Last Working Version

_No response_

Claude Code Version

2.1.92

Platform

Anthropic API

Operating System

Ubuntu/Debian Linux

Terminal/Shell

VS Code integrated terminal

Additional Information

_No response_