{"version":"2.1.288","anchor":"auto-mode-denial-messages-may-offer-an-allow-rule-tool-name","canonical_anchor":"background-task-permission-hint-now-names-the-specific-tool","heading":"Denial messages now name the right tool for an allow rule","tier":"notice","area":"Auto Mode","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288\/e\/auto-mode-denial-messages-may-offer-an-allow-rule-tool-name","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288","markdown":"### Denial messages now name the right tool for an allow rule\n\nWhen an action is blocked, the hint about adding a permission rule now names the actual tool instead of always saying Bash, and is left out where it does not apply\n\n**Unclear.** The wording of the message that uses this is not shown.\n\n**What**\n\nWhen Claude Code blocks an action, its message can suggest adding a permission rule to your settings so the action is allowed next time. That hint has changed:\n\n- It used to always say \"the user can add a Bash permission rule to their settings\", shown unless `omitSettingsRuleHint` was true. It now reads \"the user can add a permission rule for\" the specific tool, using `allowRuleToolName`, and is left out when that is not set.\n\n- The message builder for auto mode denials (where an automatic check refuses an action) now works out `allowRuleToolName` and passes it in, alongside `autoModeConsentFlow`. It is not offered for tools that need you to interact or that do not allow always-allow rules.\n\n**Why**\n\nIf a non-Bash tool is blocked, you are now pointed at the correct kind of rule, and you are not told to add a rule for tools that cannot have one.\n\n- Area: Auto Mode\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}