{"version":"2.1.281","anchor":"settings-file-edit-guard-adds-desktop-app-symlink-and-manag","canonical_anchor":"settings-file-edit-guard-adds-desktop-app-symlink-and-manag","heading":"Settings-file edit guard adds desktop-app, symlink and managed-policy refusal messages, but the path is off in this build","tier":null,"area":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/settings-file-edit-guard-adds-desktop-app-symlink-and-manag","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### Settings-file edit guard adds desktop-app, symlink and managed-policy refusal messages, but the path is off in this build\n\nRefusal messages for settings-file edits via the desktop app, symlinks or managed policy exist but cannot run in this build\n\n**What**\n\nNew code picks a reason for refusing an edit to a Claude Code settings file and sends back a matching message:\n\n- `\"card\"`: in the Claude desktop app, the edit applies only if you approve it on its permission card.\n\n- `\"linked\"`: the path reaches a settings file through a symbolic link, a shortcut that points to another file.\n\n- `\"policy\"`: the path is, or may be, a `managed-settings.json` file or the file given with `--settings`.\n\n- `\"review\"`: the existing staging for `\/settings-review`.\n\nEvery message tells the model not to try again. This code cannot run in this build. It needs an internal switch set to true while running and a helper that always answers no.\n\n**Why**\n\nFor now nothing changes. The messages show the edits that are meant to be refused: edits through a link, edits to policy-controlled files, and desktop-app edits you have not approved."}