Quick answer
Claude Code documents pro prompt allowance as No prompt count is published; five-hour limits were doubled on 2026-05-06. Anthropic defines Pro as the Pro allowance, shared across Claude and Claude Code, and no longer publishes a prompts-per-window estimate.
Verified Sep 17, 2026Official source
Current limits
| Constraint | Current value | Scope | Verified source |
|---|---|---|---|
| Pro prompt allowanceAnthropic defines Pro as the Pro allowance, shared across Claude and Claude Code, and no longer publishes a prompts-per-window estimate. | No prompt count is published; five-hour limits were doubled on 2026-05-06 | Pro | AnthropicSep 17, 2026 |
Why does this limit matter?
Repository size, task complexity, parallel sessions, and auto-accept behavior can materially change prompt consumption.
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?
- Run /status in Claude Code and confirm that subscription authentication—not API billing—is active.
- 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
- The earlier prompt ranges predate the May 2026 doubling of Claude Code five-hour limits and the removal of the peak-hours reduction; they are retained 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