{"version":"2.1.228","anchor":"relaunching-claude-code-keeps-your-selected-model","canonical_anchor":"relaunching-claude-code-keeps-your-selected-model","heading":"Relaunching Claude Code keeps your selected model","tier":"notice","area":"Models","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.228\/e\/relaunching-claude-code-keeps-your-selected-model","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.228","markdown":"### Relaunching Claude Code keeps your selected model\n\nRestarting after an update keeps the model you picked instead of reverting to the default.\n\n**What**\n\nWhen the CLI restarts itself, it now passes `--model` with the model you had selected, so an update relaunch or a renderer switch no longer drops you back to the default model.\n\n**Details**\n\n- Appended next to the existing `--add-dir`, `--effort` and `--permission-mode` arguments.\n- Omitted when the selection is the default, when running a mantle deployment, or when it equals the configured fallback model.\n- Applies to the auto-update relaunch (\"Switching from \u2026 to latest\") and to `\/tui` renderer switching.\n\n**Evidence**\n\n`--model`\n\n- Area: Models\n- Names: `--model`\n- Tier: You'll notice\n- Useful: 5\/5\n- Signal: 2\/5"}