Claude Code Reset Times & Quota Rules

Identify the five-hour and weekly windows

For subscriptions with included window-based usage, the session window is five hours, and weekly or model-specific restrictions may also apply. Read each row in /usage or Claude Settings → Usage; the session timer is not the weekly timer. A five-hour reset does not promise that a separately exhausted weekly window has recovered. Verify the affected window in the official display and confirm your next request can proceed.

Choose your next step

1. Find the restriction: open /usage and distinguish session, weekly, and model-family limits.
2. A reset time is available: record its date, time, and time zone for that specific limit; do not apply it to every window.
3. The time is missing: keep it unknown and prepare local tests or the next task. Check the account again after any saved countdown ends.

Match the action to the limit

• Only an Opus or Sonnet limit: use /model to choose an available model outside that family. Shared session and weekly allowance must still remain.
• A shared session or weekly limit: changing models does not replenish it. Wait for that window or consider separately billed usage; see options after reaching a limit.

Example: if Opus is blocked but /usage still shows shared allowance, try Sonnet. If the weekly allowance is also exhausted, switching to Sonnet will not remove that block. This is a decision example, not a promise about your account. Official error guidance.

Record each restriction and reset time

A session window may be exhausted while weekly allowance remains. A model-family restriction is also distinct from an account-wide usage restriction. Record the limit name, remaining allowance, and reset time separately; one timestamp does not describe every window.

Use the date, time, and time zone shown in the official interface. Do not infer them from a fixed weekday or billing date. If no reset time appears, record it as unknown.

Terminal and web activity can share subscription usage

With Pro or Max subscription authentication, Claude Code and Claude web access share subscription usage. When investigating terminal consumption, account for activity through other interfaces on the same account.

Membership in the same workspace does not by itself establish that every member shares one allowance. Consult the applicable plan and account terms for the metering rules of team seats.

Work to prepare while waiting

• Run local static checks and existing tests independently, and handle work that does not require AI.
• Record completed work, unresolved issues, and the next action.
• Save the official reset time in a local timer and check the account again when it expires. The timer does not monitor actual allowance or control whether Claude Code resumes execution.

If considering API-key access, first check the authentication method, billing account, and applicable limits. API work follows its associated billing path and does not reset subscription allowance; it should not be described as unlimited.

Which clients can wait and continue?

In Claude Code v2.1.234 or later, an interactive terminal session signed in with a claude.ai subscription can wait and resume after reset. Keep it open and confirm the waiting message. For resets more than 24 hours away, or with automatic continue disabled, use /rate-limit-options to choose a wait. Background sessions and -p runs do not offer it. Sleep or permission prompts can require your return. In Desktop, the session-limit card has its own checkbox; the weekly-limit card does not. See waiting conditions and cancellation and Desktop limits.

Remote Control and agent-team teammate sessions require someone at their terminal to start the wait through /rate-limit-options. API-key, cloud-provider and usage-based billing sessions do not offer this subscription-reset wait. After resuming, check that the task actually continues; it can still stop for permissions or another exhausted window.