[Bug] Excessive token usage spike after OAuth reauthentication in Claude Code

Bug Description
Okay, so I'm a Max member. I pay $100 a month, and I use Claude Code in my terminal. I've been using the 1 million context for almost a month now, no problems. I always check my current session usage time on the website, normally within a 1 million context window by the time I get to the end where I got a compact conversation, or before or around. I should say, yeah, I don't have any issues. I don't have any usage issues; I get through the whole thing just fine, but I was in the middle of working, because I sit down and I work with this. I work on this about 18 hours a day. I've been doing this for the last 14 months with this product, so I'm pretty very well intimate and very familiar with what's going on and how it works.

I was in the middle of working; I got an OAuth error. It was error 500, so I had to log back in. It took me like five attempts to log back in, so I logged back in, and when I did, I sent a message. My current session usage on the website was like 38%. Total, I was at 800,000 tokens, and it was only at 38%. I sent one message, and it spiked me all the way to 100%, and it told me I had to wait until it recharged. Luckily, I was about 20 minutes away from recharge, so I switched over to the API so I can keep working, because I'm in the middle of building something. I'm working on something, and once it recharged and went to zero, I switched back over to my subscription and sent one message. It jumped my usage 30%. I'm like, what the hell?

I was like, that might be a bug, so I sent another message, because I'm in the middle of working. I had to get things back on track. Sent another message; it was another 31% usage. I'm like, well, this is unsustainable, what the hell? I compacted the conversation at 800,000 instead of 900,000, and I turned down the think to low instead of medium, so now it's back to the normal 1-2% every message. I had to spend $10 in the API just to keep my conversation going to debug the problem, which I shouldn't have had to pay $100 a month for. I'm sitting at 70% usage with 3 hours and 44 minutes left until it recharges. That's unsustainable and that's unrealistic.

I can't get that current session time back. I can't get the money back that I spent to keep my conversation going, because I'm in the middle of working. It's not like I can just walk away from this and say, well, it broke, so it'll fix itself. No, that's no way. Like I said, I've been working with this product for 14 months, for about 18 hours, if not longer, a day. I literally live on my machine working, so I'm very familiar with how the product works. I'm very familiar with how to manage my tokens, how to manage my session usage limits, my weekly limits, all of it. For me to be at 70% usage, with still almost 4 hours left on the timer, that's a fundamental problem, and it was because of an authorization. I got the API error 500 or whatever it is. You can look at my account usage; you can see how everything works, how my sessions work, how long I'm on here, everything. For me to send one message and to get a 30% bump in usage, that shouldn't happen. I sent another one. It was a 20. It was a 31% bump in the usage. I'm like, what the hell?

I came back to the conversation because I thought the conversation was bugged, which I'm pretty sure it was, because now it's back around 1-2% like normal. I still have 4 hours before it recharges, so I have to be very careful how many messages I send in the next 4 hours, or I'm gonna hit 100% again, which I don't ever get close to 100% before it recharges. That's how I spaced my stuff; I have a system, and I space everything out just right, so I never hit 100%, but for that to happen, it's a fundamental issue, especially for what I'm paying a month. I shouldn't have these problems. I'm sure the heck shouldn't be getting double charged for using this when this is a default model for someone like me.

When I wanted to send the bug report in and at least get it on paper and get someone to look into it, because it's a fundamental problem and it's unsustainable for people that are power users like I said, I'm using this at my business. This is my job. I'm a CEO of my own company. I'm building for the last 14 months with your guys's product solely with your guys's product. I don't want to stop using your guys's product because of issues like this. I mean, I've gotten so many people to come over to your guys's product because of my experience with it, so one of the best products I've ever used in my life. It's fundamentally changed how I work and how I build and what I'm capable of building, so I want to keep working with it, but I'm not going to be able to if I can only send three messages and blast through a 5-hour usage window. I appreciate your time for looking into this, and I apologize that this messag…
Note: Content was truncated.