A session can reset while your weekly allowance is still exhausted.
Claude Code subscription usage has multiple counters. Anthropic’s limits documentation describes five-hour sessions and weekly limits, except for verified Ultra accounts. Start with Settings > Usage to identify the limit and its reset time before changing plans or authentication.
Read the session and weekly counters separately
A five-hour period begins with your first message and resets five hours later. Weekly limits reset at a fixed, account-specific time. A session reset does not restore a weekly allowance that has already run out. Max and Ultra also have a separate weekly Fable limit.
Imagine a session reset due in 30 minutes and a weekly reset due tomorrow. If the weekly counter is exhausted, waiting those 30 minutes won’t lift the restriction. The useful information is the counter that stopped the request, rather than the shortest countdown visible on the page.
Conversation length, model choice, and effort affect consumption. Anthropic does not offer a universal number of coding requests that fits every repository. A long context and a short edit can use different amounts of the same allowance.
The terminal and IDE do not create separate allowances
Anthropic’s consumer-plan guide says supported IDE usage counts toward the limits shared across Claude and Claude Code. Moving from a terminal to an IDE with the same subscription therefore does not create a fresh budget.
Check the authentication method as well. Anthropic warns that a configured ANTHROPIC_API_KEY makes Claude Code use API authentication instead of the subscription, with API usage charges. If a bill differs from what you expected, establish which account and billing route handled the request before buying more capacity.
Wrap-up can finish an existing step, within limits
The wrap-up allowance may let an eligible response continue briefly after a five-hour limit. It needs Claude Code 2.1.277 or later and an eligible account in the gradual rollout. It applies to work already in progress, not a new request sent after the limit.
Pro can receive it once per weekly period. Max can receive it at a five-hour boundary within weekly limits. Verified Ultra accounts have no five-hour cap, so this allowance does not apply to them. Anthropic describes temporary-limit Ultra cases separately. Wrap-up consumption still counts toward the weekly allowance.
The allowance is capped and discretionary. It may end before the whole task finishes. If usage credits are enabled, work can continue on those credits under the applicable settings and spending limit after the included allowance ends. Wrap-up does not switch paid usage credits on.
Diagnose the restriction before spending more
First record the blocking counter and reset time. Then confirm the signed-in account, model, and authentication route. Review usage-credit settings only if you want paid continuation. This sequence separates a timing problem from a billing choice.
We checked Anthropic’s published guidance, not a particular subscriber’s allowance. The documentation is current, but it doesn’t show that Anthropic introduced a new quota policy this week. Our cloud-session coverage concerns a different feature and credit announcement. Which counter interrupts your work most often?
Abdessalam Alaoui
I'm Abdessalam Alaoui, founder of Musthave.AI. I write practical guides to AI models, tools, generative media.
