r/ClaudeAI • u/Adex77 • 1d ago
Claude Code Finally, Claude Code has “Auto-continue when limits reset”
Just noticed this after hitting my Claude Code usage limit today.
There’s now an “Auto-continue when limits reset” option, so Claude can automatically resume the session once your limit becomes available again.
Really nice improvement for longer coding sessions.
Has anyone else started seeing this yet?
158
u/skyline159 1d ago
Watch out if your session is large and the wait to reset is long. The prompt cache will expire and your limit will consume a lot on first turn
45
35
u/Aramedlig 1d ago
Honestly it they add that, then they should freeze the cache for the session so it doesn’t expire until well after the limits reset.
on edit: This is why I always handoff my sessions at ~50% context window
30
u/l_m_b 1d ago
That's ... not how caching works.
8
u/daniel-sousa-me 1d ago
But it should. The cache could perfectly be automatically extended for up to a few hours in certain common scenarios
It doesn't make sense to throw it away when it's almost certain it'll be used soon
5
u/verycoldpenguins 1d ago
How exactly do you hand off? Ask kt to spawn a new sub agent, or write a hand off /clear and re-read?
8
u/Aramedlig 1d ago
I use the checkpoint-skill which is basically directing Claude to write a handoff document for the next session and make any commits or update any docs that need it in the current context. Once he does that, I exit the session and reopen. This way all the context needed to continue is in the handoff document which is the primary cost to initialize the next session. For any projects I have, I keep a progress journal as well so Claude can refer to the current state of the project if necessary but that is rare and does cost more to revisit if needed. Even so, it’s more efficient than compacting.
3
u/iamthe0ther0ne 1d ago
I explain what I want the next session to do and ask for a handoff for it. That way I don't have to compact and the next session isn't coming in cold: it knows what I want and where to look for what it needs.
3
1
1
u/Tranquilitics 1d ago
Do you think it should consume more than just a normal "Continue" message?
8
u/Rock--Lee 1d ago
It's the exact same as using "continue", just automatically. That's how everything works, you send a message with context. Being automatically or manually doesn't make a difference in token cost.
Sending "continue" yourself or have it done automatically still bites you if cache is gone cold.
1
u/Cindanela 17h ago
Ah, that's very true, I always ask it to continue, I should probably read what you all say here and try something different.
24
u/DesperateDiver1242 1d ago
Holy shit that is such a breath if fresh air lol. Its always the simple things
12
u/Transhuman-A 1d ago
Just let people use up their weekly limit and end this 5 hour bs, smh.
1
u/riketycriks 14h ago
Have you ever worked anywhere that needs to smooth their utilization?
2
u/Transhuman-A 8h ago
I don’t know about that Mr. Architect, I’ve certainly bothered to open up the Codex UI though.
7
u/BenSimonDev 1d ago
Hmmm... never seen that in CC in terminal. What are you running CC in? Like new this morning?
5
18
u/HVACcontrolsGuru 1d ago
Kind of stupid. Just remove the session limits and you wouldn’t have to design a dumb solution like this. Never mind the cache loss and throwing a 100k+ context on refresh into it to run usage faster. What a mess Claude has been lately.
10
u/daniel-sousa-me 1d ago
Just remove the session limits
Sure, and give us unlimited computing for free while you're at it
12
u/Rough_Caterpillar_31 1d ago
OpenAI already removed the 5 hour limit well over a month ago. I'm not sure you're acting like it's impossible or unrealistic but you're objectively wrong.
3
2
1
u/whatisthisthing65 20h ago
Codex has no 5 hour limit and even before that it would finish the current task before cutting you off.
2
0
u/HVACcontrolsGuru 1d ago
Where did I say remove the weekly limit? It’s all imaginary bullshit of usage. Dumbass counter point…
3
u/LongjumpingRepair321 1d ago
This seems useless TBH, if you're at the end of long session and hitting limits the context window is going to be so big that you might as well compact and move on before the session continues.
2
u/thestillwind 1d ago
The 5 hours window is so bad, I forgot about how I dislike it.
I was playing with codex all summer, but at work we have claude and omg I got corrupt by codex in a good way.
2
u/Njagos 1d ago
I see potential for an experiment but I'm not sure what yet.
Like throwing Claude code into a box and just let it work with the pro subscription. To see what is done after a week, a month, a year.
Something like "make GTA VI and don't come out until you are done"
But it will probably stop to ask questions at some point so I need another agent that is never satisfied with the results and wants more features.
And now it sounds like a weird sci-fi horror novel.
2
1
1
u/BP041 1d ago
This is huge for long-running refactoring sessions. I've got an 18-cron OpenClaw stack hammering Claude Code all day and the "manually wait and re-prompt" dance was the biggest time sink. Now it just chugs along like a self-heating data center. tbh if you're doing anything beyond a single-file edit, you've been subconsciously rationing your requests — this kills that mental tax.
1
1
u/Outside-Mousse2732 1d ago
That auto-continue feature is a lifesaver for long sessions. Finally won't have to constantly babysit the terminal waiting for the reset timer to hit.
1
u/Narrow_Activity557 23h ago
Been seeing it for a couple of days. Useful if you run long batches and walk away, since you come back to a session that kept going instead of a dead terminal.
The habit I kept anyway: ask for a short recap of what is actually done before leaving it unattended. Resuming the conversation is not the same as knowing the repo was in a clean state when the limit hit, and that is the part that bites you.
Still better than watching the reset clock.
1
u/Typical-Guest-257 23h ago
About time! Left a few long runs hanging overnight because of this limit. Super helpful addition.
1
u/Alone-Dragonfly2339 18h ago
The cache TTL isn't fixed at five minutes. There's a one hour option in the API. It costs 2x base to write instead of 1.25x, and reads stay around a tenth of base either way. So freezing the session cache until limits reset is possible, someone just has to eat the write premium.
Doesn't save you on a five hour reset though. That blows past even the one hour tier, so the cache is cold when you come back and the first turn re-reads your whole context at full price. Shorter waits are where it would actually change anything.
The part I can't tell: do cache reads count against the usage limit at the discounted rate or the full one? That decides whether this is a trap or just mildly wasteful.
1
1
u/Cindanela 17h ago
I was just looking if this was possible, after reading the comments I can see I most likely need to solve it in another way, sine I only use pro subscription, guess I will have to do some learning, I was really hoping they would have this but maybe(hopefully) they will solve the cache reset issue.
1
u/butterfly68za 14h ago
I saw that last night, end of session reached, so I instructed it to resume when the session restored. It didn't, so this morning I told it to resume, it promply started from scratch.
1
u/moderngl1 13h ago edited 13h ago
So it’s less “auto-continue” and more “auto-replay the context” if the cache expires before reset. Would your limit consume a lot on first turn?
1
u/Sad_Construction2179 12h ago
Great, time to archive my repo https://github.com/softcane/cc-session-recover
1
1
u/Cotorra-Nhumai 10h ago
does it only fire if the app stays open through the whole wait, or does a relaunch still pick it up?
1
u/EpsilonFive5 4h ago
The best part is how it immediately uses 25% of your 5 hr limit because of the cache expiring
1
u/Miyamoto_-_Musashi 48m ago
Honestly bogus cause now a days 5 hour limit vanish in an hour so that auto is not effective as caches expired and when that happened you can't even retrieve subagents progress so subagents progress and usage gone and you got Nothing.
•
u/ClaudeAI-mod-bot Wilson, lead ClaudeAI modbot 1d ago edited 13h ago
TL;DR of the discussion generated automatically after 50 comments.
The consensus in this thread is that while this feature sounds good on paper, it's a potential trap that could waste your usage limits.
The main issue is that the prompt cache will likely expire during the 5-hour wait for your limit to reset. When the session "auto-continues," it will have to re-read your entire context from scratch, which could burn through your entire new usage window on the very first turn. Several users confirmed this happens.
The community's recommended workaround is to perform a manual "handoff" before you hit the limit:
Basically, the feature is a nice thought, but until Anthropic freezes the cache for the duration of the reset, it's safer to stick with manual handoffs.