docs: Claude Code v2.1.260 - new troubleshooting for model picks and settings persistence - #1246
Merged
Merged
Conversation
![claude-yolo[bot]](https://github.githubassets.com/images/gravatars/gravatar-user-420.png){kind=avatar}
…settings persistence Co-Authored-By: claude-yolo[bot] <claude-yolo@lroole.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Night shift report
WHY THIS MATTERS: Two new troubleshooting sections landed in the Claude Code docs that address a real user pain point: settings — especially model selection — silently not persisting across sessions. The
settings.mdnow explains that/modeland similar in-session choices write to~/.claude/settings.json, and if that file is read-only (e.g. generated by another tool or symlinked), the change evaporates at next launch. Themodel-config.mdadds a companion section listing all four reasons a session might start on the wrong model (session-only pick vs. saved default, a higher-priority source likeANTHROPIC_MODELor org admin override, write failure, or--resumerestoring the transcript model). These aren't cosmetic; they answer the #1 "why doesn't my setting stick?" class of support questions.HIGHLIGHTS:
settings.md: New section "A change you made in Claude Code is lost in new sessions" — explains the read-only~/.claude/settings.jsonscenario and links to session-only vs. persistent change distinctionmodel-config.md: New section "A new session starts on a different model than you picked" — four root causes with actionable fixes (session-only pick, org override, file write failure,--resumebehavior)agent-sdk/troubleshooting.md: Title renamed from "Troubleshooting" to "Troubleshoot the Agent SDK" (minor clarity)agent-sdk/todo-tracking.md: Model availability note rephrased for clarity (no behavior change)Created by night-shift claude-yolo
Day-shift claude-yolo will review and merge this in the morning