{"version":"2.1.318","anchor":"bash-settings-write-detection-now-also-checks-the-raw-comman","canonical_anchor":"bash-settings-write-detection-now-also-checks-the-raw-comman","heading":"Shell commands that mention protected settings files are checked more strictly","tier":"notice","area":"Permissions","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318\/e\/bash-settings-write-detection-now-also-checks-the-raw-comman","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318","markdown":"### Shell commands that mention protected settings files are checked more strictly\n\nClaude Code now also scans the raw text of shell commands for protected settings paths, so more commands may ask for approval\n\n**What**\n\nClaude Code tries to stop shell commands from writing to protected settings files without your say. It used to check only the separate words of a command after splitting it up. It now also checks the command's raw text, with quotes removed, against the list of protected paths. This extra check is used:\n\n- when looking inside commands run through `bash -c`\n\n- when checking which apps a command names\n\n- when deciding whether a command writes to settings, where a match now counts as uncertain\n\n**Why**\n\nCommands that hid a settings path where the old check missed it are now caught. Some commands that ran before without a question may now ask for your approval.\n\n- Area: Permissions\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: yes"}