Max 20x plan hitting daily limit with reduced usage — limits appear silently tightened (April 28-29, 2026)

Summary

Max 20x subscriber ($200/month) consistently hitting daily usage limits on April 28-29, 2026, despite reduced usage compared to previous weeks. No change in workflow, plugins, or usage patterns. Running Claude Code v2.1.123 — well past the v2.1.116 fixes from the April 23 postmortem.

Environment

• Plan: Max 20x
• Claude Code version: 2.1.123
• Model: claude-opus-4-6[1m]
• Effort level: high
• Platform: macOS (Darwin 25.3.0)

What happened

• Hit the daily usage limit on both April 28 and April 29, 2026
• Usage patterns have not increased — if anything, usage was less than usual
• The rate limit message mentioned high subagent usage, but subagent usage has not increased
• Previously sustained heavier workloads on the same plan without hitting limits

What has NOT changed

• Same plugins enabled (no new plugins added recently)
• Same model (claude-opus-4-6[1m])
• Same effort level (high)
• Same types of tasks (coding, research, code review)
• Researcher plugin (which spawns many Opus subagents) was disabled during this period
• No increase in session length or frequency

The broader pattern

This is not an isolated report. There is a documented pattern of Max plan limits being silently reduced over time:

• Issue #28848 (Feb 2026): "Max plan usage limits silently reduced since Claude 4.6 release" — labeled "invalid" with no explanation
• Issue #17084 (Jan 2026): "Opus 4.5 usage limits significantly reduced since January 2026"
• Issue #4203 (earlier): "Significant Rate Limit Reduction in Claude Code — Impact on Professional Workflow — $200 max plan"
• Issue #41788 (Apr 2026): "Max 20 plan: rate limit 100% exhausted within ~70 minutes after reset"

Each time, users report the same thing: limits suddenly tighter with no change in usage. Each time, no concrete response from Anthropic about what changed.

The transparency problem

The core issue is that Anthropic does not publish concrete limits for any plan tier. The official help article (Using Claude Code with your Pro or Max plan) says only that "usage limits are shared across Claude and Claude Code." No token budgets, no 5-hour window sizes, no weekly caps — just opaque percentages.

This means:

1. Users cannot verify whether they are getting what they pay for
2. Anthropic can adjust limits at any time without announcing changes
3. When users report tighter limits, it's impossible to prove because there are no published baselines
4. The "20x" in "Max 20x" is meaningless without knowing 20x of what

Compute constraint context

Anthropic's CEO Dario Amodei has publicly described the company as compute-constrained. An Anthropic engineer confirmed on March 26, 2026 that session limits drain faster during peak hours (5am–11am PT), affecting ~7% of users. The April 23 postmortem acknowledged three bugs causing 10-20x token inflation but stated they were fixed in v2.1.116.

If limits are being dynamically adjusted based on available compute capacity, that is understandable from an infrastructure perspective — but it needs to be communicated transparently, not silently applied to paying subscribers.

What I'm asking for

1. Publish concrete limits for each plan tier — token budgets per 5-hour window, weekly caps, and how subagent usage counts. Users paying $200/month deserve to know what they're buying.

1. Announce limit changes when they happen. Silent reductions erode trust. A simple status page update or changelog entry would suffice.

1. Investigate whether limits were reduced between April 23-28, 2026, after the postmortem fixes shipped. If the v2.1.116+ fixes reduced Anthropic's server-side costs (by fixing cache bugs that inflated usage), was the "savings" passed on to users, or were limits tightened to absorb it?

1. Clarify whether the 1M context model variant (claude-opus-4-6[1m]) has different effective limits than the standard context model. If serving 1M context costs more compute, do Max 20x users get fewer requests when using it?

1. Provide per-session token breakdowns that show exactly where tokens are going — main conversation vs. subagents vs. system prompt vs. thinking — so users can make informed decisions about their usage.

Labels

bug, usage-limits