{"version":"2.1.283","anchor":"powershell-path-check-helpers-now-return-the-checked-paths-i","canonical_anchor":"powershell-path-check-helpers-now-return-the-checked-paths-i","heading":"PowerShell path checks now pass on the actual file paths","tier":"internal","area":"Windows","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283\/e\/powershell-path-check-helpers-now-return-the-checked-paths-i","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283","markdown":"### PowerShell path checks now pass on the actual file paths\n\nChecks on PowerShell commands now return the list of paths they accepted instead of a simple yes or no\n\n**Unclear.** What, if anything, this changes in the permission prompts a user sees is not confirmed.\n\n**What**\n\nClaude Code checks PowerShell commands before running them, including the file paths named after the command, after `-Path` or `-LiteralPath`, and after `-f` or `--force`. Two of these checks used to answer only yes or no. They now return the list of paths they accepted, or nothing when they reject the command.\n\n**Why**\n\nThe rest of the permission logic can now work with the specific paths involved in a PowerShell file command rather than a bare yes or no.\n\n- Area: Windows\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}