{"version":"2.1.288","anchor":"clearer-messages-when-timeoutenv-wrappers-cant-be-pre-chec","canonical_anchor":"clearer-messages-when-timeoutenv-wrappers-cant-be-pre-chec","heading":"Shorter, clearer reasons when a Bash command option 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\/clearer-messages-when-timeoutenv-wrappers-cant-be-pre-chec","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288","markdown":"### Shorter, clearer reasons when a Bash command option can't be checked in advance\n\nPermission prompts for timeout, env, command -p\/-v and jobs -x now use shorter wording that names the option that couldn't be checked\n\n**What**\n\nBefore running a shell command, Claude Code tries to work out what it will do. When an option makes that impossible, the permission prompt explains why. Those explanations were rewritten to be shorter and to name the option involved:\n\n- `timeout` and `env` wrappers now name the option, for example \"'timeout ${u}' can't be checked before it runs\". Before: \"timeout has an option or value (...) that cannot be checked in advance\".\n\n- `jobs -x` now reads \"What 'jobs -x' starts can't be checked before it runs\". Before: \"'jobs -x' runs its argument as a command, so what it will run cannot be checked in advance\".\n\n- The `command -p` and `command -v` messages are also shorter.\n\n**Why**\n\nWhen Claude Code asks you to approve a wrapped command, the prompt now tells you more directly which part it couldn't check.\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"}