Verified history
Anthropic withdrew the published Pro message estimate
The Pro plan help article now says message capacity varies with message length, files, conversation length, model and feature; no per-five-hour count is published. Detection date recorded; no effective date given.
Do not size workloads on the old 45-message estimate.
Current monitored baseline
HyperObserve currently monitors 2 scoped observations for Claude. The baseline covers plan capacity, usage reset window. 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 |
|---|---|---|---|
| plan capacityCapacity is plan-relative rather than a universal message count and varies with workload. | Free: limited; Pro: standard; Max: 5× or 20× Pro | Personal plans | AnthropicSep 17, 2026 |
| usage reset windowClaude and Claude Code subscription activity can draw from the same window. | Rolling five-hour window | Pro and Max | AnthropicSep 17, 2026 |
Tracked constraints and impact
Consumer Claude plan capacity, reset windows, and disclosed usage factors. 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 Usage Limits by Plan
Claude Usage Limits by Plan, verified against Claude's official documentation with scope, implementation impact, caveats, and a direct check.
Claude Five-Hour Usage Window
Claude Five-Hour Usage Window, verified against Claude's official documentation with scope, implementation impact, caveats, and a direct check.
Claude Pro Message Limit Estimate
Claude Pro Message Limit Estimate, verified against Claude'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 baseline. HyperObserve links directly to them so you can confirm the live wording before making a production decision.
Free, Pro, Max 5x, and Max 20x capacity table
Shared usage limits across Claude and Claude Code, five-hour window, /status guidance