{"version":"2.1.288","anchor":"model-restored-from-resumed-session-via-shared-helper-resto","canonical_anchor":"model-restored-from-resumed-session-via-shared-helper-resto","heading":"Resuming a session now checks the saved model before switching to it","tier":"notice","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288\/e\/model-restored-from-resumed-session-via-shared-helper-resto","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288","markdown":"### Resuming a session now checks the saved model before switching to it\n\nResuming a session now checks the saved model before using it, and a saved \"default\" resolves to the current default model\n\n**Unclear.** It is unclear where the logic for restoring a model after a refused launch model is used, so its effect is unknown.\n\n**What**\n\nWhen you resume an earlier session (pick up a past conversation where it left off), Claude Code switches back to the model that session was using. That step now goes through a shared check that confirms the saved model is valid before applying it. A saved value of \"default\" is turned into whatever the default model currently is. Claude Code also has new logic for restoring a model when the model chosen at launch was refused.\n\n**Why**\n\nThis may change which model a resumed session uses, particularly one run without the interactive interface.\n\n- Area: Sessions\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}