Hitting the five-hour limit used to stop Claude mid-change. A new wrap-up allowance lets it finish the job, and limits went up 20%.
If you hit your five-hour limit mid-task, Claude used to stop on the spot, sometimes halfway through a change. Now it gets a small allowance to finish the job.
The wrap-up allowance
When the limit lands mid-task, Claude borrows a small, fixed amount from your weekly limit and tries to finish what it was doing. How often you get it depends on your plan:
| Plan | Wrap-up allowance |
|---|---|
| Pro | Once a week |
| Max | Every time you hit a five-hour limit |
| Team Premium | Every time you hit a five-hour limit |
More headroom on top
- Five-hour limits are up 20%.
- Everyone on Pro, Max and Team got one full usage reset. It sits in Settings > Usage until 22 October.
- Cloud sessions are out of research preview and included in your plan at no extra cost. Existing Pro and Max subscribers also get a one-time credit ($100 on Pro, $250 on Max), spent before your normal plan usage. Claim it with
/claim-creditby 7 October.
Two smaller fixes in the same spirit
- Send now keeps running work (v2.1.281). Ctrl+Enter (or Ctrl+X Ctrl+S) sends your queued messages straight away. Anything still running, like a long test command, moves to the background instead of being cancelled.
- The dangerous rm prompt now times out (v2.1.281). In unattended auto mode or
--dangerously-skip-permissionsruns, a flagged rm waits two minutes for an answer, then denies the command with a rewrite hint. The session keeps going instead of hanging.
Do this week
- Run
/claim-creditbefore 7 October. - Use your reset before 22 October.
Build Faster.
Earn Smarter. Stress Less.
See how AI can help your business communicate better with your customers
Start now
Lorem ipsum dolor sit amet consectetur
No items found.
