A committed settings file granting host-specific write paths blocks session startup with instructions.
What's wrong with this entry?
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.
- A hard refusal with no override.
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.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.247
Warning when
~/.claude.jsoncannot be watched for outside editsBoth mention json
-
v2.1.246
Local file reads route through the storage backend when it serves the space
Both mention json
-
v2.1.224
Plugin eval can validate and report its own JSON output
Both mention json