The Claude logo. Image: Anthropic
Hitting your Claude Code limit halfway through a change is about to get a lot less painful. Instead of stopping dead mid-edit when you run out of your 5-hour session allowance, Claude Code will now try to find a graceful stopping point and wrap up what it’s doing, Anthropic’s ClaudeDevs account announced on Friday. The post has already racked up hundreds of thousands of views:
Claude Code will now try to find a graceful stopping point when you hit your 5-hour limit mid-task, instead of cutting off mid-edit.
— ClaudeDevs (@ClaudeDevs) September 25, 2026
It gets a small, fixed allowance pulled from your weekly limit to wrap up what it can.
What’s changing
Until now, running out of your 5-hour allowance meant Claude Code simply stopped, wherever it happened to be. That could leave a file half-rewritten, a refactor split across a codebase or a test suite in pieces, and you’d either tidy up by hand or wait for the limit to reset before Claude could pick up the thread.
Now, when the limit hits mid-task, Claude Code shows “Usage limit reached” followed by “Wrapping up” and the time your limit resets, as seen in the demo video in Anthropic’s post. While it’s wrapping up, it gets what Anthropic calls “a small, fixed allowance” to reach a sensible place to stop. It won’t finish a big job, but it should leave your code in a state that makes sense rather than halfway through an edit.
Who gets it
In a follow-up post, ClaudeDevs said the wrap-up allowance is rolling out gradually, and how often you get it depends on your plan:
- Pro: once a week.
- Max and Team Premium: every time you hit a 5-hour session limit.
If you still need to keep going after the wrap-up, you can carry on with extra usage, Anthropic’s pay-as-you-go option. According to Claude’s help centre, extra usage is billed at standard API rates, and you switch it on under Settings > Usage with a monthly spending cap.
It isn’t free usage
The catch is in the small print: the allowance isn’t extra. It’s “pulled from your weekly limit,” so every wrap-up eats a little into the weekly cap that sits above the 5-hour windows. Anthropic hasn’t said how big the allowance is.
That matters because the weekly cap is what heavy users bump into. Anthropic raised weekly Claude Code limits by 25% from September 14, but a temporary 50% boost ended the day before, so, as Anthropic itself admitted to BleepingComputer and others, that worked out to a 17% cut from what users had over the summer. Developers are already watching closely: the maintainers of Spillway, an open-source tool that tracks Claude usage, opened an issue to check whether the wrap-up allowance quietly drains the weekly pool.
At the time of writing, the feature doesn’t appear in Claude Code’s changelog or help pages. The announcement on X is the only official word so far.
Part of a run of limit tweaks
It’s the latest change Anthropic has made to how Claude’s limits feel in practice. It recently added a one-time “Reset for free” button for usage limits and handed Claude Code users up to $250 in credit for cloud sessions. Both, like this change, are aimed at the moment developers find most frustrating: running out of Claude halfway through the job.
Why it matters
Coding agents now work on big, multi-file tasks for long stretches, and being cut off halfway is one of the biggest complaints about subscription limits. A graceful wrap-up doesn’t give you more Claude, but it makes hitting the ceiling far less destructive, and it’s a sign Anthropic knows its limits are a bigger sore point than its models.
Sources: ClaudeDevs on X, Claude Help Center, BleepingComputer, Spillway on GitHub.
