{"version":"2.1.287","anchor":"bash-static-analysis-refusal-message-reworded","canonical_anchor":"bash-static-analysis-refusal-message-reworded","heading":"Clearer reasons when a shell command needs your permission","tier":"notice","area":"Permissions","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287\/e\/bash-static-analysis-refusal-message-reworded","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287","markdown":"### Clearer reasons when a shell command needs your permission\n\nReasons shown when Claude Code cannot check a shell command ahead of time now say it 'cannot be checked in advance'\n\n**What**\n\nBefore running a shell command without asking, Claude Code checks what the command will do. When it cannot, it asks your permission and shows a reason. Several of those reasons have been reworded:\n\n- A command with an option it does not recognise now reads \"command has an option or value (...) that cannot be checked in advance\". It used to say the command with that flag \"cannot be statically analyzed\".\n\n- `timeout` with an option it cannot check now reads \"timeout has an option or value (...) that cannot be checked in advance\".\n\n- `timeout` with a duration it cannot read now reads \"timeout has a duration ('...') that cannot be checked in advance\".\n\n- `jobs -x` now reads \"'jobs -x' runs its argument as a command, so what it will run cannot be checked in advance\".\n\n**Why**\n\nThe permission prompt now explains in plain words why Claude Code is asking, instead of using the term \"statically analyzed\".\n\n- Area: Permissions\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}