{"version":"2.1.290","anchor":"shell-command-safety-reason-strings-shortened","canonical_anchor":"shell-command-safety-reason-strings-shortened","heading":"Shorter explanations in permission prompts for project tools and relative paths","tier":"notice","area":"Permissions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290\/e\/shell-command-safety-reason-strings-shortened","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290","markdown":"### Shorter explanations in permission prompts for project tools and relative paths\n\nPermission prompts now say 'it runs a project tool, such as make or npm' and 'it runs a file by a relative path'\n\n**What**\n\nWhen Claude Code asks your permission before running a shell command, it shows a short reason why the command needs your approval. The reasons for two kinds of command now read:\n\n- 'it runs a project tool, such as make or npm', which replaces a longer line listing make, npm, pytest and cargo\n\n- 'it runs a file by a relative path', for a command that runs a file named by its location relative to the current folder\n\n**Why**\n\nYou will see this simpler wording in the permission prompt for these commands.\n\n- Area: Permissions\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 0\/5\n- Scope: individual\n- Heads-up: no"}