{"version":"2.1.314","anchor":"shell-command-safety-check-paths-now-allowed-in-some-case","canonical_anchor":"shell-command-safety-check-paths-now-allowed-in-some-case","heading":"Commands that start with a ~ path can now be flagged as running a file by relative path","tier":"notice","area":"Bash Tool","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314\/e\/shell-command-safety-check-paths-now-allowed-in-some-case","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314","markdown":"### Commands that start with a ~ path can now be flagged as running a file by relative path\n\nThe shell safety check that flags running a file by relative path can now catch paths starting with ~ in some cases\n\n**Unclear.** Under what condition a command starting with ~ is now flagged.\n\n**What**\n\n`~` is shorthand for your home folder. Claude Code checks shell commands before running them, and one check flags a command because \"it runs a file by a relative path\". That check used to ignore anything starting with `~`. It now counts such text in some cases, under an extra condition.\n\n**Why**\n\nThis changes which commands get flagged when Claude Code decides whether to ask your permission or approve a command on its own. Commands that run something from a `~` path may now be flagged where they were not before.\n\n- Area: Bash Tool\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}