{"version":"2.1.300","anchor":"update-restart-refused-when-launch-settings-mcp-config-f","canonical_anchor":"update-restart-refused-when-launch-settings-mcp-config-f","heading":"Update restart is refused if a launch settings file is gone","tier":"notice","area":"Elsewhere","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300\/e\/update-restart-refused-when-launch-settings-mcp-config-f","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300","markdown":"### Update restart is refused if a launch settings file is gone\n\nClaude Code will not restart a session onto a new version if a file passed with --settings or --mcp-config can no longer be read\n\n**What**\n\nClaude Code can restart a running session onto a newly installed version. Before doing so, it now checks that any file you passed with `--settings` or `--mcp-config` when you started the session can still be read. If one cannot, it refuses to restart and shows a message beginning \"Can't restart this session. It was started with\".\n\n**Why**\n\nWithout this, a restart could quietly come back without settings or MCP servers from a file that was deleted or moved after launch. If you see this message, restore the file or start a fresh session.\n\n- Area: Elsewhere\n- Names: `--settings`, `--mcp-config`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: yes"}