1M Context Window: Documentation Contradiction Between Blog Post and FAQ

Documentation Type

Unclear/confusing documentation

Documentation Location

https://code.claude.com/docs/en/model-config#extended-context-with-1m

Section/Topic

Extended context

Current Documentation

the docs currently says:
"On Max, Team, and Enterprise plans, Opus is automatically upgraded to 1M context with no additional configuration."

and also:
Blog post (March 13, 2026) — 1M context is now generally available
"1M context is now included in Claude Code for Max, Team, and Enterprise users with Opus 4.6."
"Claude Code Max, Team, and Enterprise users on Opus 4.6 will default to 1M context automatically."
No distinction between Max 5x and Max 20x. The word "generally available" is in the title.

Changelog v2.1.75 (March 13, 2026)
"Added 1M context window for Opus 4.6 by default for Max, Team, and Enterprise plans (previously required extra usage)"
Again, "Max" — no tier distinction.

What's Wrong or Missing?

Claude Code FAQ (updated this week) — CONTRADICTS ALL OF THE ABOVE
"Long context support is currently limited to some Claude Code users on Max 20x plans, so it's available only to a small number of users. The 1M context window is not generally available for all Claude Code users yet, including those accessing Claude via the API."
This directly contradicts the blog title ("generally available"), the changelog ("Max plans"), and the model config docs ("Max plans").

Suggested Improvement

I previously had working 1M context on this same plan and version. It stopped working without any notification or changelog entry.
If 1M is only for "some Max 20x users", then the blog post, changelog, and model config docs are all misleading. They need to be corrected immediately.
If 1M is intended for all Max plans, then the FAQ is wrong and the server-side entitlement check is broken for Max 5x users.
Either way, silently revoking a feature that was previously available — without any user notification, changelog entry, or pricing page update — is not acceptable. Users make purchasing decisions based on documented capabilities.

Request:
Clarify the actual eligibility for 1M context across Max 5x, Max 20x, Team, and Enterprise plans.
If the eligibility has changed, update the blog post, changelog, and model config docs to match reality.
If this is a rollout issue, provide a timeline for when Max 5x users will regain access.
Going forward, communicate feature removals through the same channels used to announce them.

Impact

High - Prevents users from using a feature

Additional Context

_No response_