Claude Code runs on the same plan usage as the rest of Claude, but the terminal surface makes the limits feel different: you see them mid-task, in a workflow where stopping is expensive. This guide maps which budgets apply, where the CLI shows reset information, and which community-reported behaviors are worth tracking (verified 2026-11-14).
Which budgets apply inside Claude Code§
Claude Code is included with Pro, Max, Team and Enterprise plans and draws from the plan's usage family: a five-hour session window plus a weekly limit on Pro and Max; Ultra accounts (verified) face the weekly budget without the five-hour cap. The exact allowances and any current promotions are visible in your account and in the tool's usage output — not in any static table.
Because the budgets are shared with web chat, heavy chat usage earlier in the day shrinks what Claude Code has left. If the CLI reports a limit sooner than expected, check the same account in the Claude app — the session window may already be partly spent.
Reading the CLI's usage output§
When a limit triggers, the CLI's message names the constraint (session or weekly) and shows when it resets. That displayed time is the authoritative one for your account. Community tools exist that estimate usage; they are approximations and no substitute for the app's own numbers.
The official model-usage guidance for Claude Code also leans on context management: clearing between unrelated tasks and compacting long sessions reduces how much allowance each unit of work burns. That is the supported lever for doing more inside the same window — it changes consumption, not the clock.
Community reports: reduced, boosted and stretched§
r/ClaudeCode threads document the moving parts: reports of weekly allowances being cut by double-digit percentages in a single adjustment, later restored or boosted; reports of reset windows stretching well past five hours; and periodic fresh-week grants around major launches. Anthropic does not publish a changelog for limit adjustments, so these reports are the only early-warning system — treat them as signals to verify in your own account, not as facts.
What no report supports is a bypass. There is no documented command or setting that resets Claude Code limits early; "reset command" tricks circulating in forums are not real. If limits bind your work, the supported paths are plan changes, pacing, or API usage with its own metering.
FAQFAQ
Do Claude Code and web chat share the same limits?
Yes — usage draws from the same plan family, so web usage counts against what Claude Code has available. The reverse is true as well.
Is there a /reset command in Claude Code?
No documented command resets usage limits. /clear and /compact manage context (which affects how fast allowance burns) but do not touch the clocks.
Why did my Claude Code limits get cut?
Community reports document occasional reductions (one described a 17% weekly cut) followed later by adjustments. Allowances move with promotions and load; your account display is the only current source of truth.
Does Claude Code have its own weekly reset?
It surfaces the same weekly limit the plan carries, with the same account-fixed reset day and time described in the official documentation.