[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

Status Closed — not planned
Maintainer reply None cached
Activity 1 comment · opened Jun 10, 2026 · closed Jul 20, 2026

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

The opusplan model 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 the opus model setting and does not extend to opusplan.

What's Wrong or Missing?

The v2.1.172 release notes ship a fix:

Fixed opusplan model setting not shipping with 1M context in plan mode for entitled users; the opusplan[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 the opus model setting for users who are entitled to extended context (Max, Team, Enterprise). The opusplan[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.

View original on GitHub ↗

This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗