{"version":"2.1.304","anchor":"protected-path-check-gains-per-call-exceptions-and-a-flag-fo","canonical_anchor":"protected-path-check-gains-per-call-exceptions-and-a-flag-fo","heading":"Protected file check gains exceptions and a git config option","tier":"notice","area":"Permissions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.304\/e\/protected-path-check-gains-per-call-exceptions-and-a-flag-fo","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.304","markdown":"### Protected file check gains exceptions and a git config option\n\nThe check for protected files can now skip named files per request and only checks git config inside .git folders when asked\n\n**Unclear.** It is not clear which actions pass these exceptions or the git config option, so which writes now prompt differently is unknown.\n\n**What**\n\nClaude Code keeps a list of protected files, and writing to one of them asks for your permission first. The check that decides this used to look only at the file path. It now also accepts:\n\n- A set of exceptions: a file on the protected list is not treated as protected if it is in this set.\n\n- An option for git config files below `.git` folders: that check now runs only when the option is switched on.\n\nThe check also now compares names in ways that allow for differences in letter case and in how Unicode characters are encoded, so two spellings of the same name are caught.\n\n**Why**\n\nThis affects which file writes ask you for permission first.\n\n- Area: Permissions\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}