{"version":"2.1.290","anchor":"bash-command-safety-reasons-shortened","canonical_anchor":"bash-command-safety-reasons-shortened","heading":"Shorter reasons when a shell command needs your approval","tier":"notice","area":"Permissions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290\/e\/bash-command-safety-reasons-shortened","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290","markdown":"### Shorter reasons when a shell command needs your approval\n\nThe reasons Claude Code gives for asking you to approve a shell command are shorter, with some explanations in brackets removed\n\n**What**\n\nWhen Claude Code asks you to approve a shell command, it gives a reason. Several of these reasons are now shorter and worded differently:\n\n- \"it unsets PATH\" and \"it runs a file by a relative path\" no longer carry an explanation in brackets.\n\n- One reason now reads \"it unsets a GIT_CONFIG variable\".\n\n- Other wordings changed too, such as \"this machine cannot verify\".\n\n**Why**\n\nThe text you see in permission prompts is different and quicker to read.\n\n- Area: Permissions\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 0\/5\n- Scope: individual\n- Heads-up: no"}