[DOCS] Model configuration docs still describe Opus 4.6 as the current 1M-context Opus model

Resolved 💬 2 comments Opened Apr 22, 2026 by coygeek Closed Apr 29, 2026

Documentation Type

Incorrect/outdated documentation

Documentation Location

https://code.claude.com/docs/en/model-config

Section/Topic

opus model alias table entry and the "Extended context" section

Current Documentation

The docs currently say:

| opus | Uses the latest Opus model (currently Opus 4.6) for complex reasoning tasks | Opus 4.6 and Sonnet 4.6 support a 1 million token context window for long sessions with large codebases. Availability varies by model and plan. On Max, Team, and Enterprise plans, Opus is automatically upgraded to 1M context with no additional configuration.

What's Wrong or Missing?

Changelog v2.1.117 says Claude Code fixed Opus 4.7 sessions that were showing inflated /context percentages and autocompacting too early because the app was still computing against a 200K window instead of Opus 4.7's native 1M context window.

That makes the current model documentation outdated: it still tells users that the latest/current Opus model is 4.6 and that the relevant 1M-context Opus model is Opus 4.6. Users reading the model docs do not get an accurate explanation of why Opus 4.7 sessions should use a 1M context window for /context percentages and auto-compaction thresholds.

Suggested Improvement

Update https://code.claude.com/docs/en/model-config to reflect the current Opus model and context behavior:

  1. Change the opus alias entry so it no longer says the latest Opus model is "currently Opus 4.6" if Opus 4.7 is now the default/current Opus model.
  2. Update the "Extended context" section to state that Opus 4.7 sessions use a native 1M context window where applicable.
  3. Add a short clarification that /context, status-line context percentages, and auto-compaction thresholds are based on the active model's actual context window.
  4. If provider-specific behavior differs, explicitly call out when 1M is automatic versus when users still need a pinned [1m] model variant.

Impact

Medium - Makes feature difficult to understand

Additional Context

Affected Pages:

| Page | Context |
|------|---------|
| https://code.claude.com/docs/en/model-config | Alias table still says opus currently means Opus 4.6, and the extended-context section still describes Opus 4.6 as the 1M-context Opus model |
| https://code.claude.com/docs/en/azure-ai-foundry | Pinning guidance already tells Foundry users to set an Opus 4.7 model ID to use the latest model, which conflicts with model-config's current/latest Opus text |

Total scope: 2 pages affected

Source: Changelog v2.1.117

Exact changelog entry: Fixed Opus 4.7 sessions showing inflated /context percentages and autocompacting too early — Claude Code was computing against a 200K context window instead of Opus 4.7's native 1M

View original on GitHub ↗

This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗