[DOCS] [Advisor] `/advisor` picker pre-selects the last saved advisor model, but `advisor.md` does not say the picker refuses to pre-select a model blocked by `availableModels`

Documentation Type

Missing documentation (feature not documented)

Documentation Location

https://code.claude.com/docs/en/advisor

Section/Topic

The "Use the /advisor command" subsection in docs/en/advisor.md, and the "Restrict model selection" section in docs/en/model-config.md. The v2.1.174 changelog fixes a case where /advisor would pre-select a saved advisor model that is no longer permitted by the availableModels allowlist, but neither page documents the interaction between the /advisor picker and the availableModels policy.

Current Documentation

docs/en/advisor.md (line 41-49) currently says:

"### Use the /advisor command Run /advisor without arguments to open a picker listing the available advisor models, or pass the model directly: `` /advisor opus ` Your selection is saved to advisorModel in your user settings and persists across sessions. If your current main model does not support the advisor, the selection is still saved and activates when you switch to a [compatible main model](#choose-an-advisor-model) with [/model`](https://code.claude.com/docs/en/model-config)."

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

"## Restrict model selection Enterprise administrators can use availableModels in managed or policy settings to restrict which models users can select. When availableModels is set, users cannot switch to models not in the list via /model, --model flag, or ANTHROPIC_MODEL environment variable. Elements of a [fallback model chain](#fallback-model-chains) outside the list are dropped. ``json theme={null} { "availableModels": ["sonnet", "haiku"] } ` ### 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 /advisor dialog pre-selecting a saved advisor model that is blocked by the availableModels allowlist"

The closest related changelog entry is v2.1.165 (line 30 in changelog.md):

"Fixed availableModels restrictions not being applied to subagent model overrides, the agent dispatch model picker, and the advisor model"

What's Wrong or Missing?

A. The availableModels enforcement list does not include the /advisor picker

model-config.md line 116 enumerates where availableModels is enforced: "users cannot switch to models not in the list via /model, --model flag, or ANTHROPIC_MODEL environment variable." The /advisor picker and the saved advisorModel setting are not in the list, even though the v2.1.165 changelog already documented that availableModels applies to the advisor model. The v2.1.174 fix implies the picker pre-selection respected the saved setting but ignored the allowlist, and the docs still do not say the /advisor picker is gated by availableModels.

B. The advisor.md page does not say the picker filters by availableModels

A user who sets availableModels and then runs /advisor to change the advisor will see the picker filtered. A user whose saved advisorModel is later blocked by a policy change opens /advisor and (before v2.1.174) sees the blocked model pre-selected. Neither flow is described.

C. The "Default option" exemption note is the wrong analogue

model-config.md line 126 says Default is "not affected by availableModels". The /advisor picker has no equivalent Default row — every entry is a named model. Users may reasonably infer from the Default exemption that all picker entries are exempt. The v2.1.174 fix is the opposite: named advisor entries are not exempt.

Suggested Improvement

Option A: Comprehensive fix

1. In docs/en/model-config.md (line 112-128), add /advisor to the availableModels enforcement list and add a paragraph noting the picker behavior:

> "When availableModels is set, users cannot switch to models not in the list via /model, --model flag, ANTHROPIC_MODEL environment variable, the /advisor picker, or the saved advisorModel setting. As of v2.1.174, the /advisor dialog will not pre-select a saved advisor that is no longer in the allowlist."

1. In docs/en/advisor.md (line 41-49), add a sentence to the "Use the /advisor command" subsection:

> "The picker only lists models allowed by your organization's availableModels policy (see Restrict model selection). As of v2.1.174, the picker no longer pre-selects a saved advisorModel that has been removed from the allowlist; it opens on the first allowed entry instead."

Option B: Minimum fix

Add the picker filter note to advisor.md only. Leave the model-config.md cross-reference 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 | 112-128 | "Restrict model selection" — enforcement list omits the /advisor picker and saved advisorModel |
| https://code.claude.com/docs/en/advisor | 41-49 | "Use the /advisor command" — does not say the picker is filtered by availableModels or describe pre-selection behavior |
| https://code.claude.com/docs/en/settings | 214 | availableModels row in the Available settings table — does not list the /advisor picker as an enforcement point |
| https://code.claude.com/docs/en/changelog | 22 | Sole mention of the v2.1.174 fix; the v2.1.165 fix is at line 30 and is the only related entry |

Total scope: 3 pages affected, plus the changelog.

Cross-references:

• https://code.claude.com/docs/en/commands — /advisor is documented as a command; the picker filter behavior lives in advisor.md and model-config.md and should be cross-referenced from the /advisor row
• https://code.claude.com/docs/en/sub-agents — the same availableModels allowlist applies to subagent model overrides (per the v2.1.165 changelog at line 30); the new model-config.md paragraph should be co-located with the existing subagent note

Version: v2.1.174 (June 12, 2026)