Quick answer
Claude documents pro message count as No fixed message count is published. Anthropic states that the number of messages varies with message length, attached files, conversation length, and the model or feature used.
Verified Sep 17, 2026Official source
Current limits
| Constraint | Current value | Scope | Verified source |
|---|---|---|---|
| Pro message countAnthropic states that the number of messages varies with message length, attached files, conversation length, and the model or feature used. | No fixed message count is published | Pro | AnthropicSep 17, 2026 |
Why does this limit matter?
Planning must use the in-product usage indicator rather than a published per-window count.
This value is scoped to Pro; a different plan, runtime, model, endpoint, region, or account can produce a different effective constraint.
What should you check?
- Compare the current conversation length and attachment load with the remaining usage shown by Claude.
- Confirm the exact plan, model, runtime, endpoint, region, and account that serve the failing workload.
- Record the observed value, response headers or configuration, timestamp, and source without logging secrets.
Important caveats
- Earlier help-centre guidance gave an approximate 45-message figure; that estimate is no longer published and is kept only as history.
- 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