{"version":"2.1.287","anchor":"permission-denial-message-can-omit-the-settings-rule-hint","canonical_anchor":"permission-denial-message-can-omit-the-settings-rule-hint","heading":"Permission denial messages can now leave out the settings rule tip","tier":"notice","area":"Permissions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287\/e\/permission-denial-message-can-omit-the-settings-rule-hint","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287","markdown":"### Permission denial messages can now leave out the settings rule tip\n\nSome denied-permission messages can now skip the tip about adding a Bash permission rule to your settings\n\n**Unclear.** It is not clear which parts of Claude Code ask for the tip to be left out.\n\n**What**\n\nWhen Claude Code is blocked from running a command, the message it shows can end with a tip: add a Bash permission rule to your settings. A permission rule is an entry in your settings file that allows or blocks a command in advance. Parts of Claude Code can now ask for that tip to be left out.\n\nBefore this, the tip was dropped only under the conditions that already existed.\n\n**Why**\n\nSome denial messages may no longer suggest editing your settings, so the absence of that tip does not mean the message is broken.\n\n- Area: Permissions\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}