{"version":"2.1.288","anchor":"permission-answers-can-no-longer-add-exception-paths-to","canonical_anchor":"permission-answers-can-no-longer-add-exception-paths-to","heading":"Permission answers can no longer add exception rules starting with !","tier":"notice","area":"Permissions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288\/e\/permission-answers-can-no-longer-add-exception-paths-to","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288","markdown":"### Permission answers can no longer add exception rules starting with `!`\n\nDeny or ask rules arriving in an answer to a permission request are now dropped with a warning if they start with `!`\n\n**What**\n\nAn answer to a permission request can carry extra rules for Claude Code to follow. Deny rules (refuse an action) and ask rules (check with you first) in such an answer are now dropped, with a warning, when they start with `!`, which marks an exception to a rule. Before, only allow rules arriving this way were filtered. An answer may only add restrictions.\n\n**Why**\n\nAn exception added to a deny or ask rule would loosen it. This stops an answer from widening permissions that way.\n\n- Area: Permissions\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}