> Loosing it for a couple of days is more palatable

Sorry, I'll just be "that guy" for a moment. Assuming that access is cut at a random time during the week, the average number of days without Claude would be 3.5. That's not reasonable as it's dependant on usage. So assume that you've always been just shy of hitting the limit, and you increase usage by 50%, then you'd hit the limit 4.67 days in. Just 2-3 hours shy of the weekend - a sort of reward for the week's increased effort.

Have a blessed Thuesday.

My original post wasn't clear and that's my fault, but I am taking that into account. When I said "that's it for the week" I meant "the remainder of the week." It's just a mouthful to write "the remainder of the week" each time.

And... well, I am worried that I could do something stupid or accidental on Monday and Tuesday and then loose access with more than half of the week left, especially since, as everyone else has noted, Claude doesn't show you how close to the limit you are until you've almost hit it. (That said, I also appreciate that it doesn't warn me too early, or I would be constantly watching the usage tick up well before I actually need to worry about it.)

A couple of weeks ago, Claude got into some kind of weird loop where it just kept saying something like "now I need to add the code continuation" over and over and over again. I had auto-accept turned on, and it was chugging for several hours before I realized something was wrong and stopped it. Who knows how much usage that burned! Luckily, it happened late in the evening, so I knew my usage would reset the next day anyway. But IIRC it was also a Monday evening...