{"version":"2.1.273","anchor":"denyask-permission-messages-now-append-the-matched-rules-o","canonical_anchor":"denyask-permission-messages-now-append-the-matched-rules-o","heading":"Deny\/ask permission messages now append the matched rule's own text","tier":"notice","area":"Permissions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.273\/e\/denyask-permission-messages-now-append-the-matched-rules-o","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.273","markdown":"### Deny\/ask permission messages now append the matched rule's own text\n\nPermission deny\/ask messages now show the exact rule text that triggered the block\n\n**What**\n\nWhen a tool call is denied or requires confirmation ('ask') because it matched a specific permission rule, the message shown to the user now appends that rule's own associated hint text, including in cases where the match happened on a nested subcommand.\n\n**Why**\n\nThis makes it clear which permission rule caused a block or prompt, and shows any custom message attached to that rule, instead of leaving the user to guess which rule fired.\n\n- Area: Permissions\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}