Verified limit lookup

Claude Code Reset Time & Shared Usage

Claude Code Reset Time & Shared Usage, verified against Claude Code's official documentation with scope, implementation impact, caveats, and a direct check.

Verified Aug 22, 20261 official source
Quick answer

Claude Code documents subscription reset and scope as Resets every 5 hours; shared with Claude. The terminal warns as capacity falls and can offer separate pay-as-you-go API usage.

Verified Aug 22, 2026Official source

Current limits

ConstraintCurrent valueScopeVerified source
subscription reset and scopeThe terminal warns as capacity falls and can offer separate pay-as-you-go API usage.Resets every 5 hours; shared with ClaudePro and MaxAnthropicAug 22, 2026

Why does this limit matter?

Switching surfaces does not create a new subscription allowance when both products share the same plan budget.

This value is scoped to Pro and Max; a different plan, runtime, model, endpoint, region, or account can produce a different effective constraint.

What should you check?

  1. Run /status, verify the login type, and decline API credits if the goal is to stay within the subscription.
  2. Confirm the exact plan, model, runtime, endpoint, region, and account that serve the failing workload.
  3. Record the observed value, response headers or configuration, timestamp, and source without logging secrets.

Important caveats

  • API Console credits are a separate billing system and require an explicit decision to use them.
  • Treat the official source and live account configuration as authoritative if they differ from this verified snapshot.
HyperObserve reports the documented platform constraint. Your application, SDK, gateway, provider, region, or account can impose a lower effective limit.
Related

Related references and tools

Found an outdated limit? Report it.