Themata.AI

AI is changing the world. Don't stay behind. Clear summaries, community insight, delivered without the noise. Subscribe to never miss a beat.

Privacy

Contact

Back to all news

claude anthropic developer-tools bug-reports

Pro Max 5x quota exhausted in 1.5 hours despite moderate usage

github.com

April 12, 2026

6 min read

🔥🔥🔥🔥🔥

67/100

Summary

The Pro Max 5x plan for Claude Code has reportedly exhausted its quota in just 1.5 hours despite moderate usage. Users are experiencing unexpected quota depletion issues.

Key Takeaways

The Pro Max 5x plan's quota was exhausted in 1.5 hours despite moderate usage, raising concerns about token accounting.
Cache read tokens appear to count at full rate against the rate limit, negating the benefits of prompt caching for quota purposes.
During heavy development, the system consumed 24.4M effective tokens per hour, while moderate usage led to an unexpected consumption of 70.5M tokens per hour.
Each API call sends the full context as input, resulting in significant quota consumption, especially when cache read tokens are not discounted as expected.

Read original article

Community Sentiment

Negative

Positives

The recent UX improvements to prompt caching are a step in the right direction, potentially reducing the frequency of costly cache misses during long sessions.
Users report that switching to the Codex plan has resulted in a more generous quota and improved accuracy for their specific tasks, indicating better performance in certain use cases.
Despite some issues, the Codex model is perceived as a better deal compared to Claude Code, suggesting a competitive edge in terms of quota management.

Concerns

Many users are experiencing significant performance regressions with Claude Code, including prolonged exploration loops that lead to rapid quota exhaustion.
The recent change in prompt caching behavior has left users frustrated, as it appears to negatively impact token usage and overall efficiency.
There are concerns that the quota limits are becoming increasingly restrictive, making it difficult for users to utilize the service effectively for their work.