[DOCS] Model config page says `opusplan` does not get the automatic 1M upgrade; v2.1.172 makes `opusplan` ship with 1M context in plan mode
Open 💬 0 comments Opened Jun 10, 2026 by coygeek
Documentation Type
Incorrect/outdated documentation
Documentation Location
https://code.claude.com/docs/en/model-config
Section/Topic
The opusplan model setting subsection (~line 177–190)
Current Documentation
Theopusplanmodel alias provides an automated hybrid approach: ... The plan-mode Opus phase runs with the standard 200K context window. The automatic 1M upgrade described in Extended context applies to theopusmodel setting and does not extend toopusplan.
What's Wrong or Missing?
The v2.1.172 release notes ship a fix:
Fixedopusplanmodel setting not shipping with 1M context in plan mode for entitled users; theopusplan[1m]workaround now also correctly switches to Opus in plan mode
The quoted paragraph is now wrong for entitled users (Max, Team, Enterprise) and contradicts the new opusplan[1m] alias behavior.
Suggested Improvement
Replace the last paragraph with:
The plan-mode Opus phase now uses the same automatic 1M context upgrade as theopusmodel setting for users who are entitled to extended context (Max, Team, Enterprise). Theopusplan[1m]alias also forces the 1M window and switches to Opus in plan mode. For other plans, the plan-mode phase stays on the 200K window.
Impact
High - Prevents users from using a feature
Additional Context
Version: v2.1.172. The [1m] alias table earlier in the page (around line 37–38) only lists opus[1m] and sonnet[1m]; opusplan[1m] should be added there too.