{"version":"2.1.287","anchor":"shell-wrapper-rejection-message-reworded","canonical_anchor":"shell-wrapper-rejection-message-reworded","heading":"Plainer reason when a command that runs another command is blocked","tier":"notice","area":"Permissions","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287\/e\/shell-wrapper-rejection-message-reworded","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287","markdown":"### Plainer reason when a command that runs another command is blocked\n\nThe reason shown for commands that run their argument as another command now says what they will run cannot be checked in advance\n\n**What**\n\nSome commands take another command as their argument and run it. Claude Code cannot check ahead of time what those will do. The reason it gives now reads \"can run its argument as a command, so what it will run cannot be checked in advance\". Before, it said the command \"runs its argument as a command\" and \"cannot be statically analyzed\".\n\n**Why**\n\nOnly the wording changed. The new text explains the problem without jargon.\n\n- Area: Permissions\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 0\/5"}