[FEATURE] Max plan usage limits silently reduced since Claude 4.6 release
### Preflight Checklist - [x] I have searched [existing requests](https://github.com/anthropics/claude-code/issues?q=is%3Aissue%20label%3Aenhancement) and this feature hasn't been requested yet - [x] This is a single feature request (not multiple features) ### Problem Statement ## Problem Since the Claude 4.6 release, I've been burning through my weekly usage cap dramatically faster on the Max plan ($200/month). This is not increased token consumption on my end — I audited my entire tooling stack looking for rogue API calls or background token drain. There are none. The caps themselves were lowered without a word. There is zero transparency around this: 1. **The actual limits are never published** — just a vague percentage with no denominator 2. **No notification when they change** — you find out by slamming into a wall mid-week 3. **No changelog, no announcement, nothing** — paying customers are left guessing ## Impact I'm paying $200/month. That's not a casual subscription. Silently pulling back what that buys is not okay. - I wasted hours investigating whether my own tooling was causing excess usage — it wasn't. It was a quiet cap reduction. - I can't scope my work for the week because I don't know what "100%" means anymore - I can't trust that the workflow I rely on today will still be viable next week - Every major model release apparently comes with a stealth nerf to what Max subscribers get ### Proposed Solution - **Publish concrete rate limits** for each p
Posted by anbeckham on Feb 26, 2026, 4:16 AM
Tags
Related issues
- 2026 - Microsoft Office 365
- [Ubuntu] `ubuntu-latest` label will use Ubuntu 26.04 in November 2026
- Gamut mapping
- [Codex Desktop] Editing and resending a queued message triggers "App-server queued follow-up no longer exists"
- [Windows] ChatGPT 26.820.60940 fails with "invalid transport in mcp_servers.codex_app"; Beta 26.727.40816 works
- [BUG]: infinite loading of videos
Raise real-world problems, find people facing the same issue, and discuss solutions.2,000 issues0 comments
github (SaaS)
2026 - Microsoft Office 365
[Ubuntu] `ubuntu-latest` label will use Ubuntu 26.04 in November 2026
Gamut mapping
[Codex Desktop] Editing and resending a queued message triggers "App-server queued follow-up no longer exists"
[Windows] ChatGPT 26.820.60940 fails with "invalid transport in mcp_servers.codex_app"; Beta 26.727.40816 works
[BUG]: infinite loading of videos
Restore GPT-5.6 Sol’s 372k Codex context window, or provide an opt-in setting
Codex Desktop for macOS repeatedly triggers `syspolicyd` / `trustd` CPU and memory runaway
[FEATURE] Max plan usage limits silently reduced since Claude 4.6 release
### Preflight Checklist - [x] I have searched [existing requests](https://github.com/anthropics/claude-code/issues?q=is%3Aissue%20label%3Aenhancement) and this feature hasn't been requested yet - [x] This is a single feature request (not multiple features) ### Problem Statement ## Problem Since the Claude 4.6 release, I've been burning through my weekly usage cap dramatically faster on the Max plan ($200/month). This is not increased token consumption on my end — I audited my entire tooling stack looking for rogue API calls or background token drain. There are none. The caps themselves were lowered without a word. There is zero transparency around this: 1. **The actual limits are never published** — just a vague percentage with no denominator 2. **No notification when they change** — you find out by slamming into a wall mid-week 3. **No changelog, no announcement, nothing** — paying customers are left guessing ## Impact I'm paying $200/month. That's not a casual subscription. Silently pulling back what that buys is not okay. - I wasted hours investigating whether my own tooling was causing excess usage — it wasn't. It was a quiet cap reduction. - I can't scope my work for the week because I don't know what "100%" means anymore - I can't trust that the workflow I rely on today will still be viable next week - Every major model release apparently comes with a stealth nerf to what Max subscribers get ### Proposed Solution - **Publish concrete rate limits** for each p
Comments (0)
No comments yet. Start the discussion.