claude-code - 💡(How to fix) Fix [DOCS] Model configuration docs still say `/model` selections persist across restarts

Documentation Type

Incorrect/outdated documentation

Documentation Location

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

Section/Topic

Setting your model and Default model behavior

Current Documentation

The docs currently say:

1. During session - Use /model <alias|name> to switch immediately, or run /model with no argument to open the picker.

Your /model selection is saved to user settings and persists across restarts. As of v2.1.117, if the project's .claude/settings.json pins a different model, Claude Code also writes your choice to .claude/settings.local.json so it continues to apply in that project after a restart. Managed settings take precedence and reapply on the next launch.

When the active model at startup comes from project or managed settings rather than your own selection, the startup header shows which settings file set it. Run /model to override for the current session.

What's Wrong or Missing?

A. /model is described with the old persistence behavior

The v2.1.144 release changed /model so it affects the current session only, but this page still says the command saves the selection to user settings and persists across restarts.

B. The new way to set a default for future sessions is missing

The page does not explain that saving a default for new sessions is now a separate action from switching the current session model. Users reading this page will expect /model itself to update their future session default.

Suggested Improvement

Update the /model documentation so it separates session-scoped switching from default-setting behavior.

Before:

Your /model selection is saved to user settings and persists across restarts.

After:

/model changes the model for the current session only.

To make the selected model the default for new sessions, open the model picker and press d to save it as your default.

Also update any related pages that currently imply /model controls the default model for future sessions.

Impact

Medium - Makes feature difficult to understand

Additional Context

Affected Pages:

Total scope: 2 pages affected

This appears stale relative to the v2.1.144 model-selection change, where /model became session-scoped and setting the default for new sessions moved to a separate picker action.