You'll noticeTier: how much it should matter to you
1Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
PermissionsArea: what it touches
ImprovementsKind: in v2.1.318,
ImprovementsSection of the release
What
Claude 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:
when looking inside commands run through bash -c
when checking which apps a command names
when deciding whether a command writes to settings, where a match now counts as uncertain
Why
Commands 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.
