{"version":"2.1.292","anchor":"model-default-switch-compares-model-families","canonical_anchor":"model-default-switch-compares-model-families","heading":"Saved default model is only replaced when the model family matches","tier":"notice","area":"Models","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.292\/e\/model-default-switch-compares-model-families","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.292","markdown":"### Saved default model is only replaced when the model family matches\n\nClaude Code now only overwrites your saved default model when your current model is in the same model family as the one being set\n\n**Unclear.** Which situations trigger this automatic overwrite of the saved default model is not clear.\n\n**What**\n\nWhen Claude Code writes a model into your user settings as your default, it now checks the model you are currently on against the model it is about to save. It only overwrites the saved model when both belong to the same model family. Before, it overwrote it whenever the current model was any model on a list.\n\nThe version that switches the model for the current session only, such as pressing `s` on a row in the `\/model` picker, now puts the model name into a standard form before using it.\n\n**Why**\n\nThis changes when an automatic update can replace the model saved in your settings. A saved default from a different model family is now left alone.\n\n- Area: Models\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}