[DOCS] [Model config] `/model` picker now exposes the Default-resolved family as its own row, but `model-config.md` does not describe the picker layout after v2.1.174

Documentation Type

Missing documentation (feature not documented)

Documentation Location

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

Section/Topic

The "Restrict model selection" → "Default model behavior" section in docs/en/model-config.md. The v2.1.174 changelog changes what the /model picker shows for the Default option on each plan, and model-config.md does not describe the picker layout at all.

Current Documentation

docs/en/model-config.md (line 124-128) currently says:

"### Default model behavior The Default option in the model picker is not affected by availableModels. It always remains available and represents the system's runtime default [based on the user's subscription tier](#default-model-setting). Even with availableModels: [], users can still use Claude Code with the Default model for their tier."

The v2.1.174 changelog entry reads:

"Fixed the /model picker hiding the model family that Default resolves to — Opus now appears as its own row on Max/Team Premium/Enterprise plans, Sonnet on Pro/Team plans, and Opus on pay-as-you-go API accounts"

docs/en/model-config.md (line 164-175) lists the per-tier defaults but does not describe how those defaults surface in the picker:

"### default model setting The behavior of default depends on your account type: Max, Team Premium, Enterprise pay-as-you-go, and Anthropic API: defaults to Opus 4.8 Claude Platform on AWS: defaults to Opus 4.7 Pro, Team Standard, and Enterprise subscription seats: defaults to Sonnet 4.6 Bedrock, Vertex, and Foundry: defaults to Sonnet 4.5"

What's Wrong or Missing?

A. The "Default model behavior" subsection does not describe what the user sees in the picker

The paragraph says Default "represents the system's runtime default" but does not say that the picker now surfaces this as a named row (Opus on Opus-defaulting tiers, Sonnet on Sonnet-defaulting tiers). Before v2.1.174 the picker only had a "Default" row, so users on tier-Sonnet plans had no way to know that selecting Default would use Sonnet; on Opus plans the family name was hidden inside the row. The fix changes that, and the docs need to describe the new layout.

B. The "default" model setting table does not cross-reference the picker

The per-tier default table enumerates which model "default" resolves to on each plan but does not link to the picker or describe how it appears. After v2.1.174, "default" is no longer just a hidden alias — it is a row with a family name.

C. availableModels interaction is not explained for the new family row

availableModels restricts what users can pick from the named-model list, and model-config.md already says Default is exempt. After v2.1.174, the picker shows both a Default row and a family-specific row (e.g. Opus), so users will reasonably ask whether availableModels: ["sonnet", "haiku"] blocks the Opus row that Default resolves to on a Max plan. The docs do not say.

Suggested Improvement

Option A: Comprehensive fix

1. In docs/en/model-config.md, replace the "Default model behavior" paragraph with a description of the picker layout:

> "### Default model behavior
>
> The /model picker always shows a Default row that resolves to the system's runtime default for your account. The picker also shows a separate row named after the family that Default resolves to on your plan — Opus on Max, Team Premium, Enterprise, Anthropic API, and Claude Platform on AWS; Sonnet on Pro, Team Standard, Enterprise subscription seats, and Bedrock, Vertex, or Foundry deployments. Both rows select the same model; the named family row exists so users can see what Default resolves to.
>
> The Default row is not affected by availableModels and always remains available. The named family row is also not affected by availableModels if your tier's default is the same family. Even with availableModels: [], users can still use Claude Code with the Default model for their tier."

1. Add a short note under the "default" model setting table (line 164-175):

> "In the /model picker, this same family is also exposed as its own named row alongside Default. See [Default model behavior](#default-model-behavior)."

1. Add a v2.1.174 release note pointer at the top of the section:

> "Added in v2.1.174: the /model picker now exposes the family that Default resolves to as its own row, so users can see which model 'Default' means on their plan."

Option B: Minimum fix

Replace the "Default model behavior" paragraph only. Leave the cross-references for a later pass.

Impact

Medium - Makes feature difficult to understand

Additional Context

Affected Pages:

| Page | Line(s) | Context |
|------|---------|---------|
| https://code.claude.com/docs/en/model-config | 124-128 | "Default model behavior" subsection — does not describe the picker layout that v2.1.174 introduced |
| https://code.claude.com/docs/en/model-config | 164-175 | "default model setting" table — no cross-reference to the picker |
| https://code.claude.com/docs/en/changelog | 14 | Sole mention of the v2.1.174 picker change; no cross-references to model-config.md |

Total scope: 1 page with two distinct gaps.

Cross-references:

• https://code.claude.com/docs/en/commands — /model is documented as a command; the picker layout lives in model-config.md and should be cross-referenced from /model's description
• https://code.claude.com/docs/en/settings#available-settings — availableModels row should mention that the Default row and the new family row are both exempt

Version: v2.1.174 (June 12, 2026)