[DOCS] No communication when removing Sonnet 1M from Max plan
Open 💬 0 comments Opened Jun 23, 2026 by marlondantas
Documentation Type
Missing documentation (feature not documented)
Documentation Location
_No response_
Section/Topic
etc
Current Documentation
_No response_
What's Wrong or Missing?
The 1M context window for Claude Sonnet was previously included in the Max subscription. At some point it was silently changed to require additional usage credits, with no announcement, email, changelog entry, or release note.
Users only discover this when the /context command shows 200k instead of 1M — with no explanation of why.
What happened:
- Sonnet 1M was included in Max
- It now requires usage credits on Max (only Opus 1M remains included)
- No communication was made about this change
Why this matters:
This kind of silent downgrade erodes trust. Price and plan changes are understandable — but users deserve to know when something they're paying for changes. A simple email or changelog note would have been enough.
Suggested Improvement
Request:
- Communicate plan/feature changes proactively (email, changelog, in-app notice)
- If a feature is being moved from "included" to "credits required", give users advance notice
Impact
High - Prevents users from using a feature
Additional Context
_No response_