{"version":"2.1.295","anchor":"remote-model-now-checks-whether-the-default-save-failed","canonical_anchor":"remote-model-now-checks-whether-the-default-save-failed","heading":"\/model now says when your default model could not be saved","tier":"notice","area":"Models","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295\/e\/remote-model-now-checks-whether-the-default-save-failed","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295","markdown":"### \/model now says when your default model could not be saved\n\nAfter switching models, `\/model` now checks whether saving it as your default worked and words its confirmation to match\n\n**What**\n\n`\/model` switches the AI model and saves it as your default for new sessions. Before, its confirmation always said either \"saved as your default for new sessions\" or \"for this session only\", with one \"with X effort\" ending.\n\nNow, when it saves your default, Claude Code checks whether that save worked and can report that it was refused or not saved. When the model was saved but the effort level was not, the ending reads \" \u00b7 X effort for this session only\".\n\n**Why**\n\nThe confirmation now matches what was actually kept, so you are not told a model or effort level is your default when it is not.\n\n- Area: Models\n- Names: `\/model`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}