Change history

Claude Code limit changes

Current and previous observations remain linked to their official sources. Detection date and effective date are kept separate when known.

Verified Aug 22, 20260 verified changes

Verified history

No verified historical change is recorded yet.
This means HyperObserve has not found sufficient first-party evidence for a dated before-and-after event. It does not mean Claude Code has never changed. Undated values are kept in the current baseline below instead of being presented as history.

Current monitored baseline

HyperObserve currently monitors 4 scoped observations for Claude Code. The baseline covers average Pro prompt estimate, average Max 5× prompt estimate, average Max 20× prompt estimate, subscription reset and scope. Each value retains its plan, product, endpoint, region, account, or runtime qualifier so a future change can be compared against the correct scope.

ConstraintCurrent valueScopeVerified source
average Pro prompt estimateThe estimate is for typical terminal use and shares capacity with Claude activity.Approximately 10–40 prompts every 5 hoursProAnthropicAug 22, 2026
average Max 5× prompt estimateThis tier also shares its limit with Claude consumer activity.Approximately 50–200 prompts every 5 hoursMax 5×AnthropicAug 22, 2026
average Max 20× prompt estimateThe estimate remains workload-dependent and shares capacity with Claude.Approximately 200–800 prompts every 5 hoursMax 20×AnthropicAug 22, 2026
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

Tracked constraints and impact

Terminal-agent prompts, shared subscription windows, models, and usage checks. A change is recorded only when it alters a constraint developers can act on, such as capacity planning, request shaping, model selection, deployment configuration, storage design, retry behavior, or account budgeting.

How a change is verified

  1. Compare the current first-party statement with the previously stored observation, including the exact plan, model, runtime, endpoint, region, and account scope.
  2. Separate a true product change from documentation clarification, temporary capacity, configurable account state, or a limit that applies to a different execution path.
  3. Preserve the old and new values, official source, effective date when disclosed, detection date, and practical impact. If those elements cannot be supported, no historical event is published.

Official sources monitored

These first-party documents support the current Claude Code baseline. HyperObserve links directly to them so you can confirm the live wording before making a production decision.

Using Claude Code with your Pro or Max plan

Shared limits, five-hour estimates, model switching, and status command

Related

Continue researching Claude Code