Verified history
Claude Code five-hour limits doubled for Pro; prompt estimate withdrawn
Anthropic announced on 2026-05-06 that Claude Code's five-hour rate limits were doubled for Pro, Max, Team and seat-based Enterprise plans and that the peak-hours reduction was removed for Pro and Max. The help centre no longer publishes prompt-count estimates.
The old prompt ranges understate current capacity; use /status and the in-product indicator.
Claude Code five-hour limits doubled for Max 5×; prompt estimate withdrawn
Anthropic announced on 2026-05-06 that Claude Code's five-hour rate limits were doubled for Pro, Max, Team and seat-based Enterprise plans and that the peak-hours reduction was removed for Pro and Max. The help centre no longer publishes prompt-count estimates.
The old prompt ranges understate current capacity; use /status and the in-product indicator.
Claude Code five-hour limits doubled for Max 20×; prompt estimate withdrawn
Anthropic announced on 2026-05-06 that Claude Code's five-hour rate limits were doubled for Pro, Max, Team and seat-based Enterprise plans and that the peak-hours reduction was removed for Pro and Max. The help centre no longer publishes prompt-count estimates.
The old prompt ranges understate current capacity; use /status and the in-product indicator.
Current monitored baseline
HyperObserve currently monitors 1 scoped observation for Claude Code. The baseline covers 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.
| Constraint | Current value | Scope | Verified 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 Claude | Pro and Max | AnthropicSep 17, 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.
Claude Code Pro Prompt Limits
Claude Code Pro Prompt Limits, verified against Claude Code's official documentation with scope, implementation impact, caveats, and a direct check.
Claude Code Max 5× Prompt Limits
Claude Code Max 5× Prompt Limits, verified against Claude Code's official documentation with scope, implementation impact, caveats, and a direct check.
Claude Code Max 20× Prompt Limits
Claude Code Max 20× Prompt Limits, verified against Claude Code's official documentation with scope, implementation impact, caveats, and a direct check.
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.
How a change is verified
- Compare the current first-party statement with the previously stored observation, including the exact plan, model, runtime, endpoint, region, and account scope.
- Separate a true product change from documentation clarification, temporary capacity, configurable account state, or a limit that applies to a different execution path.
- 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.
Shared usage limits across Claude and Claude Code, five-hour window, /status guidance