HyperObserve
Search HyperObserve
Platform hub

Claude Code limits

Terminal-agent prompts, shared subscription windows, models, and usage checks. Values below are scoped rather than flattened into one misleading platform-wide number.

Verified Aug 22, 2026Official docs
Quick answer:  Claude Code has multiple independent constraints. Match the exact plan, model, runtime, invocation mode, or server configuration shown in each row.

Current documented 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 MaxAnthropicSep 17, 2026

How to apply Claude Code limits safely

The monitored baseline covers subscription reset and scope. Treat these as separate constraints rather than one platform-wide capacity number: a workload can fit one row and still fail another because the plan, model, endpoint, runtime, region, invocation mode, or account scope differs.

  1. Match the production workload to the exact scope printed beside each value and confirm it in the active Claude Code console, configuration, or response headers.
  2. Measure the serialized request, token volume, duration, concurrency, storage, or connection demand at realistic percentiles, then preserve headroom for bursts and retries.
  3. Check every adjacent layer—client, SDK, gateway, proxy, queue, database, and downstream service—for a smaller effective limit before changing architecture.

Specific limit pages

These pages exist because the constraint has a distinct implementation or troubleshooting intent. Closely related keyword variations stay consolidated.

Compare alternatives

Official sources

Use Claude Code with your Pro or Max plan

View Claude Code change history