{"version":"2.1.242","anchor":"session-spawn-aborts-on-host-specific-write-paths-committed-","canonical_anchor":"session-spawn-aborts-on-host-specific-write-paths-committed-","heading":"Session spawn aborts on host-specific write paths committed to a repo","tier":"notice","area":"Permissions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242\/e\/session-spawn-aborts-on-host-specific-write-paths-committed-","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242","markdown":"### Session spawn aborts on host-specific write paths committed to a repo\n\nA committed settings file granting host-specific write paths blocks session startup with instructions.\n\n**What**\n\nIf 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`.\n\n**Details**\n\n- A hard refusal with no override.\n\n**Evidence**\n\n`Host-specific write-scope entries belong in the operator's user-level settings.json`\n\n- Area: Permissions\n- Names: `settings.json`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 3\/5"}