What
Claude 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".
Why
Without 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.
Names in the bundle--settings--mcp-config
The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.
Confirmed since
Anthropic's documentation has since written up --settings, on All settings.
* **Scope**: [`User or managed`](#scopes). Claude Code reads the key from managed settings. It reads the key from user settings only on a machine with no managed settings, in a session whose credential isn't a Team or Enterprise `/login`. …settings-reference see the edit
Added since
A small documentation edit on Manage multiple agents with agent view touched a line naming --settings after this was published.
2. The permission mode of the session you came from. If that session was in `bypassPermissions` mode, the new session can start in Manual mode instead, with the notice `Bypass permissions was requested at launch and ignored`. That happens …agent-view see the edit
One source agreesOne thing we can check says the same as this entry.
Anthropic's documentation agrees
A small documentation edit on Manage multiple agents with agent view touched a line naming --settings after this was published.