What
If a settings file checked into the repository grants write access to a host-specific path, the runner now refuses to start the session and tells the operator to move that entry into their user-level settings.json.
Details
- A hard refusal with no override.
Evidence
Host-specific write-scope entries belong in the operator's user-level settings.json
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Names in the bundlesettings.json
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.
Added since
A small documentation edit on Manage multiple agents with agent view touched a line naming settings.json after this was published.
If the session took its effort from your settings rather than from `--effort` or `/effort`, Claude Code reads your settings again each time it starts a process for the session. After you edit the saved effort in `settings.json`, the change…agent-view see the edit
Confirmed since
Anthropic's documentation has since written up settings.json, on Claude Code changelog.
* \[VSCode] Fixed Auto disappearing from the mode picker in new-tab or just-reloaded conversations when a project or local setting overrides the model named in `~/.claude/settings.json`changelog see the edit
One source agreesOne thing we can check says the same as this entry.
Anthropic's documentation agrees
Anthropic's documentation has since written up settings.json, on Claude Code changelog.