-
Notifications
You must be signed in to change notification settings - Fork 18.2k
[FEATURE] Max plan usage limits silently reduced since Claude 4.6 release #28848
Copy link
Copy link
Open
Labels
invalidIssue doesn't seem to be related to Claude CodeIssue doesn't seem to be related to Claude Code
Description
Preflight Checklist
- I have searched existing requests and this feature hasn't been requested yet
- 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:
- The actual limits are never published — just a vague percentage with no denominator
- No notification when they change — you find out by slamming into a wall mid-week
- 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 plan tier. Stop hiding behind percentages.
- Notify users when limits change — email, dashboard banner, anything. Silence is disrespectful.
- Show actual usage numbers, not just percentages — "75% of ?" is useless
- Changelog for limit adjustments — especially after model releases when costs change
- If you need to reduce limits, say so upfront — don't let paying customers discover it by getting cut off
Alternative Solutions
No response
Priority
High - Significant impact on productivity
Feature Category
Documentation
Use Case Example
No response
Additional Context
No response
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
invalidIssue doesn't seem to be related to Claude CodeIssue doesn't seem to be related to Claude Code