20x Max plan: weekly usage depleting abnormally fast (50% in 1.5 days) + request for restored limit visibility
Resolved 💬 3 comments Opened Apr 18, 2026 by Jilvert22 Closed Apr 21, 2026
Summary
On the Max 20x plan, the weekly usage indicator reached ~50% after only 1.5 days of use — depletion is dramatically faster than the 20x-tier budget should allow.
Observed Numbers
- Plan: Max 20x
- Time elapsed in weekly window: ~1.5 days
- Weekly usage: ~50%
- Extrapolation: if this rate continues, weekly budget would be exhausted in ~3 days (i.e. less than half a week), effectively turning a "weekly" budget into a "few-day" budget on the highest tier
Suspected Contributing Factors
- Stuck status bar (see companion issue): users cannot observe accumulation in real time, so runaway consumption goes unnoticed
- xhigh/max effort stalls: extended thinking episodes of 10+ minutes may be consuming unexpectedly large token amounts during reasoning
- Lack of transparent rate breakdown: no visible indicator of what drives consumption — tool calls, thinking, output, or background agents
- Multi-agent workloads: cmux orchestration with 6 concurrent Opus workspaces is a supported use case for Max 20x, but consumption appears to exceed reasonable expectations for this tier
Requests
- Investigate whether the 20x plan's weekly limit calculation is behaving as intended — current rate looks inconsistent with 20x advertising
- Restore the previous (pre-update) limit visibility — explicit warnings and breakdown of what is consuming budget
- Separate session vs weekly indicators with clearer distinction in UI
- Consider a higher tier if the observed consumption is the true intended cost — the current 20x may no longer be sufficient for advertised multi-agent / long-session use cases
- Make "max effort" cost explicit — if max-effort thinking is disproportionately expensive, users should see that clearly before/during use
Environment
- Claude Code v2.1.114
- Plan: Max 20x
- Model: Opus 4.7 (1M context)
- Multi-agent setup: cmux with 6 concurrent Opus workspaces
- OS: Darwin arm64 (macOS)
Related
- Companion bug report: https://github.com/anthropics/claude-code/issues/50324 (Status bar CTX indicator regression)
Additional Context
The Max 20x plan was chosen specifically to support multi-agent orchestration. If the true consumption is correct at this rate, either the plan's advertised capacity needs clearer communication, or a higher tier needs to exist — otherwise premium users cannot rely on the weekly budget for sustained work.
This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗