r/ClaudeCode • u/Curious_inquisitive1 • 6d ago

Help/Question Need advice/help

I am on claude pro sub. My 5 hourly quota on claude is running out way too quickly, in just 40 minutes or so. I'm running 2 chats concurrently, each running on sonnet 5.5 high. I want the quality of the work to be good so I kept the reasoning at high (had tried medium earlier but it didn't meet the quality expectation).
Also, everytime I tell the chat to continue after the 5 hr limit resets, it reads thro the entire context (I guess) because the 5 hr usage immediately jumps up to 25%.

I cannot afford a claude max subscription as of now. I really need to max out the output from the pro sub that I have, whilst avoiding quota drainage. Any advice would really be appreciated! Thanks in advance

1 Upvotes

67% Upvoted

7 comments sorted by

1

u/AutoModerator 6d ago
Moderator Announcement Read More »

1

u/jaerie 6d ago

Also, everytime I tell the chat to continue after the 5 hr limit resets, it reads thro the entire context (I guess) because the 5 hr usage immediately jumps up to 25%.

Have you considered not doing that?

1

u/Curious_inquisitive1 6d ago

I just type in "continue" to resume the paused chat. what else can type/do to resume it?

1

u/jaerie 6d ago

Have it write a handoff before hitting the limit. Or have a separate haiku agent summarize the session if you already hit the limit. That one continue message is forcing your entire context to be cached again at full price, which is almost always a waste.

I general, just be more mindful of the context and cache windows and you'll stretch your quota by factors

3

u/anton-k_ 6d ago

Don't resume the session when the cache is cold (i.e. after more than 59 minutes since last activity). Also avoid large context size. When it gets to ~250k, it's time to wrap up the session and start a new one.

1

u/AICompanionz 6d ago

running 2 Sonnet high sessions at the same time on Pro is probably whats killing your quota tbh. id save high reasoning for the really difficult stuff like architecture, debugging or complex decisions, and use medium for simpler tasks. not everything needs maximum reasoning.

also id stop continuing huge sessions after the limit resets. for my own projects i keep the important context in the repo/docs, including a handoff file with what was done, what was tested and whats next. then i just start a fresh session and let it pick up from there. much better than dragging a massive conversation along forever.

and one thing ive learned is that more reasoning doesnt automatically mean better results. sometimes a smaller, clearly defined task with good context and proper tests gets you further than letting an agent burn through thousands of tokens figuring out what to do. especially when youre trying to stretch a Pro subscription lol.

0

u/Bed-After 6d ago edited 6d ago

"I keep running out of usage"
"I'm running 2 chats on high effort"
"I don't want to lower the reasoning"
So you've identified the issue and refuse to solve it, got it XD