{"version":"2.1.193","anchor":"destructive-command-scope-detection","canonical_anchor":"destructive-command-scope-detection","heading":"Destructive Command Scope Detection","tier":null,"area":null,"scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.193\/e\/destructive-command-scope-detection","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.193","markdown":"### Destructive Command Scope Detection\n\n**What**\n\nA new analysis pass for Bash and PowerShell commands classifies the scope of destructive operations (e.g., `rm -rf`, `Remove-Item -Recurse`) as `cwd`, `outside_cwd`, `tmp`, or `unknown`, enabling more targeted permission prompts.\n\n**Details**\n\n- Analyzes both bash-style (`rm -rf path`) and PowerShell cmdlet (`Remove-Item -Path target -Recurse -Force`) syntax.\n- Recognizes temp-directory patterns on macOS (`\/tmp`, `\/var\/tmp`, `\/private\/tmp`), Linux, and Windows (`%TEMP%`, `AppData\\Local\\Temp`).\n- Shell expansions (`$VAR`, backticks, wildcards) cause the scope to be classified as `unknown` rather than guessing.\n\n**Evidence**\n\nNew scope detection (search for `\"destructive-target-scope parse failed\"`)"}