{"version":"2.1.314","anchor":"hook-policy-matching-supports-negation-with-a-leading-minus","canonical_anchor":"hook-policy-matching-supports-negation-with-a-leading-minus","heading":"A value in some lists can now be excluded with a leading minus","tier":"notice","area":"Settings","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314\/e\/hook-policy-matching-supports-negation-with-a-leading-minus","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314","markdown":"### A value in some lists can now be excluded with a leading minus\n\nSome list matching now treats an entry written as `-value` as an explicit exclusion of that value\n\n**Unclear.** It is not clear which setting accepts the leading-minus exclusion, so readers cannot yet rely on it.\n\n**What**\n\nClaude Code checks some lists by looking for a value in them. That check now ignores upper and lower case and extra spaces. A match still counts as allowed. An entry written with a leading minus, such as `-value`, now means that value is explicitly left out. Before, a list could only include values, not exclude them.\n\n**Why**\n\nThis gives some allow lists a way to say \"everything this covers except this one\".\n\n- Area: Settings\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}