Detailed Analysis
A Claude Code user on Reddit's r/ClaudeAI community has reported the disappearance of the "Sonnet (1M context)" option from the application's model picker following a skill installation and subsequent restart. Prior to the change, the user's model picker displayed four distinct options: a "Default (recommended)" entry pointing to Sonnet 4.6, a separate "Sonnet (1M context)" listing, Opus 4.8, and Haiku 4.5. After the skill install and restart, the standalone Sonnet (1M context) entry vanished entirely, leaving only the default Sonnet 4.6, Opus 4.8, and Haiku 4.5. Attempts to resolve the issue by removing and reinstalling the extension had no effect, prompting the user to question whether the change was intentional on Anthropic's part or an account- or configuration-level anomaly.
The significance of this issue centers on the 1 million token context window, which represents a substantially expanded capability compared to standard context offerings. For users working with large codebases, lengthy documents, or complex multi-file projects, the distinction between a standard context window and a 1M context window is operationally meaningful. If the separate listing has been removed and the feature folded silently into the "Default" option without clear documentation, users may be uncertain whether they are still accessing that extended context capability or whether it has been downgraded without notice. The user's inability to resolve the problem through reinstallation suggests the issue is likely server-side or tied to account entitlements rather than a local configuration artifact.
This kind of UI-level ambiguity reflects a broader challenge in how AI product companies communicate model capability changes to end users. As Anthropic continues to update Claude Code — which serves as a dedicated agentic coding environment — the model picker serves as a primary point of user-facing transparency about what capabilities are available. When options disappear without accompanying release notes or in-app messaging, users are left to speculate whether changes represent a consolidation of features, a rollback of access, or a bug. The lack of clarity can erode trust, particularly among power users and developers who have structured workflows around specific model configurations.
The episode also highlights the growing complexity of managing AI product surfaces that combine rapidly evolving models with layered tooling like skills, extensions, and default configurations. Claude Code's model picker is a relatively simple interface, but it sits atop a complicated backend involving model versioning, context window tiers, and account-level feature flags. The user's report that reinstalling the extension had no effect suggests that such UI elements may not be purely client-driven, and that Anthropic's backend configuration plays a determinative role in what options surface for any given account. This architecture means users have limited ability to self-diagnose or self-resolve discrepancies, which increases the support burden and visibility pressure on Anthropic to publish clearer changelogs for Claude Code updates.
Read original article →