claude-code - 💡(How to fix) Fix [DOCS] Model configuration docs omit `/model` restart persistence and pin-source indicators [1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#51771Fetched 2026-04-22 07:53:17
View on GitHub
Comments
0
Participants
1
Timeline
3
Reactions
0
Author
Participants
Timeline (top)
labeled ×3

Root Cause

Because the docs currently describe startup model selection mainly in terms of CLI args, environment variables, and settings files, readers can reasonably infer that restart behavior is determined only by those sources. That is now outdated or at least incomplete for v2.1.117.

RAW_BUFFERClick to expand / collapse

Documentation Type

Incorrect/outdated documentation

Documentation Location

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

Section/Topic

Setting your model, Control the model users run on, and Checking your current model

Current Documentation

The docs currently say:

You can configure your model in several ways, listed in order of priority:

  1. During session - Use /model <alias|name> to switch models mid-session
  2. At startup - Launch with claude --model <alias|name>
  3. Environment variable - Set ANTHROPIC_MODEL=<alias|name>
  4. Settings - Configure permanently in your settings file using the model field.

And later:

The model setting is an initial selection, not enforcement. It sets which model is active when a session starts, but users can still open /model and pick Default, which resolves to the system default for their tier regardless of what model is set to.

And in Checking your current model:

You can see which model you're currently using in several ways:

  1. In status line (if configured)
  2. In /status, which also displays your account information.

The /model command reference also only says:

Select or change the AI model. For models that support it, use left/right arrows to adjust effort level. The change takes effect immediately without waiting for the current response to finish

What's Wrong or Missing?

Changelog v2.1.117 says: "Improved /model: selections now persist across restarts even when the project pins a different model, and the startup header shows when the active model comes from a project or managed-settings pin".

The current docs do not explain that a model chosen in /model can persist across restarts, including how that persisted choice interacts with a project-level model pin.

They also do not document the new startup-header indicator that tells users when the active model comes from a project pin or a managed-settings pin.

Because the docs currently describe startup model selection mainly in terms of CLI args, environment variables, and settings files, readers can reasonably infer that restart behavior is determined only by those sources. That is now outdated or at least incomplete for v2.1.117.

Suggested Improvement

Update model-config to add a short subsection that explains:

  1. whether /model selections are session-only or persisted across restarts,
  2. how persisted /model choices interact with shared project model settings and managed pins,
  3. which source wins when Claude Code restarts, and
  4. where users can see the source of the active model.

In Checking your current model, add the startup header as a documented place to confirm the active model and note that the header can indicate when the model comes from a project pin or managed-settings pin.

In the /model command reference, add a brief note that model selections persist across restarts in current versions.

Impact

Medium - Makes feature difficult to understand

Additional Context

Affected Pages:

PageContext
https://code.claude.com/docs/en/model-configPrimary explanation of model selection, startup precedence, and where to check the current model
https://code.claude.com/docs/en/commands/model command reference
https://code.claude.com/docs/en/settingsmodel setting description and settings hierarchy that readers use to interpret pin precedence

Total scope: 3 pages affected

Source: Changelog v2.1.117

Exact changelog entry: Improved /model: selections now persist across restarts even when the project pins a different model, and the startup header shows when the active model comes from a project or managed-settings pin

extent analysis

TL;DR

Update the model-config documentation to reflect that /model selections persist across restarts and interact with project-level model pins.

Guidance

  • Add a subsection to model-config explaining how /model selections are persisted across restarts and how they interact with shared project model settings and managed pins.
  • Update the Checking your current model section to include the startup header as a place to confirm the active model and note its ability to indicate the model's source.
  • Modify the /model command reference to mention that model selections persist across restarts in current versions.
  • Review the settings page to ensure the model setting description aligns with the updated behavior.

Example

No code snippet is necessary for this documentation update, but an example of the new subsection in model-config could be:

### Persisted Model Selections
When you select a model using `/model`, your choice is now persisted across restarts. This means that even if a project pins a different model, your selected model will remain active unless you change it. The startup header will indicate if the active model comes from a project pin or managed-settings pin.

Notes

The documentation update should focus on clarifying the behavior of /model selections and their interaction with project-level settings and managed pins, ensuring that users understand how the active model is determined across restarts.

Recommendation

Apply the suggested documentation updates to reflect the current behavior of /model selections and their persistence across restarts, as this will improve user understanding and reduce confusion about model selection and precedence.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING