Denial messages now name the right tool for an allow rule
When 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
You'll noticeTier: how much it should matter to you
1Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
PermissionsArea: what it touches
Bug FixesKind: in v2.1.288,
Bug FixesSection of the release
What
When 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:
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.
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.
Why
If 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.
How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtIt is not clear which refusals now carry a tool name, so the tip may no longer appear in some places where it used to.
