{"version":"2.1.288","anchor":"bash-hook-guard-and-command-check-wording-changed","canonical_anchor":"bash-hook-guard-and-command-check-wording-changed","heading":"Shorter message when a command's effect can't be checked in advance","tier":"notice","area":"Bash Tool","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288\/e\/bash-hook-guard-and-command-check-wording-changed","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288","markdown":"### Shorter message when a command's effect can't be checked in advance\n\nWhen Claude Code can't check in advance what a command will run, the reason now reads \"What '' starts can't be checked before it runs\"\n\n**Unclear.** It is not clear what extra information is added when a guard that could not run blocks a command.\n\n**What**\n\nBefore running a shell command, Claude Code tries to work out what it will do so it can apply your permission rules. Some commands run other commands given to them, which makes that check impossible. The reason shown in that case is now shorter:\n\n- Before: \"'' can run its argument as a command, so what it will run cannot be checked in advance\"\n\n- Now: \"What '' starts can't be checked before it runs\"\n\nSeparately, when a guard fails to run and blocks the command, the block now carries some extra information. A guard is a hook, a check you configure to run before commands.\n\n**Why**\n\nThese messages appear when Claude Code stops or questions a command, so you will see the new wording.\n\n- Area: Bash Tool\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 0\/5\n- Scope: individual\n- Heads-up: no"}