{"version":"2.1.309","anchor":"powershell-set-location-allowed-when-safe","canonical_anchor":"powershell-set-location-allowed-when-safe","heading":"PowerShell Set-Location can pass the permission check when judged safe","tier":"notice","area":"Windows","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.309\/e\/powershell-set-location-allowed-when-safe","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.309","markdown":"### PowerShell Set-Location can pass the permission check when judged safe\n\nA PowerShell Set-Location command can now be allowed when a safety check passes, before the working-folder check runs\n\n**Unclear.** It is not clear what the safety check tests, so which Set-Location commands now skip the prompt is unknown.\n\n**What**\n\nIn PowerShell, `Set-Location` changes the current folder, like `cd`. Claude Code checks commands before running them to decide whether to ask you first. A `Set-Location` command now passes that check when a safety check on the command succeeds. This happens before the usual check on which folder the command moves to.\n\n**Why**\n\nThis may mean fewer permission prompts when Claude changes folders in PowerShell.\n\n- Area: Windows\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}