What happened
Claude Code plans cap how much you can use the tool each week. Hit that cap and your sessions pause until the limit resets. Claude Code 2.1.234 added automatic continuation when a claude.ai usage limit resets. You no longer need to restart the waiting session yourself. You can turn this off in /config under “Continue automatically at usage limit.”
A day later, Anthropic’s official developer account, @ClaudeDevs, announced a separate but related change: the temporary 50% increase to weekly Claude Code limits was extended through August 31. “We hope to make this a permanent change to our plans, but strong demand for our models means that capacity may be tight over the coming weeks,” the post said.
This boost has already been extended more than once this year without becoming permanent. Anthropic keeps pushing the deadline back a few weeks at a time rather than letting it lapse or locking it in.
Why it matters
The auto-continue feature removes a real annoyance: manually checking back and restarting a session after you got cut off mid-task. But it also changes what “hitting your limit” means in practice. Previously, a limit was a natural stopping point where you’d step away and decide whether to keep going. Now, if you leave a session running, Claude Code can pick back up on its own hours later without you there to see what it does first.
That matters more right now because Anthropic scheduled auto mode as the default on Pro, Max, and Team for August 14. Auto mode replaces you approving each command with a classifier, a separate AI model that reviews what Claude wants to do and decides in real time whether it’s safe to run without asking you first. Combine that with auto-continue and a session can resume and keep executing commands while you’re away, with no one reviewing the plan in real time. Individually, both features are reasonable conveniences. Together, they mean a session you thought was paused can start acting again without you noticing.
The temporary limit increase was a separate capacity announcement. August 31 was its announced endpoint, not a commitment that the higher quota would become permanent.
Who should care
Anyone running Claude Code regularly enough to hit weekly usage limits, especially if you also run in auto mode and tend to walk away from a session rather than closing it. If you rely on the limit itself as your natural checkpoint for reviewing what Claude has done, that checkpoint just got quieter.
What builders should do next
Open /config inside Claude Code and check the “Continue automatically at usage limit” setting. If you want a hard stop when you hit your limit, so you can review before continuing, turn it off. If you’re fine with automatic resumption, also check which permission mode you’re running (press Shift+Tab in the terminal to see it). Auto-continue plus auto mode is the combination worth being deliberate about, not either setting alone.
For current capacity, use your account’s usage display rather than relying on the historical August extension. If your workflow depends on the extra headroom, type /usage inside Claude Code to see how much of your quota is left and when it resets, rather than assuming the boosted limit will still apply next week.
End of article