Unclear What, if anything, this changes in the permission prompts a user sees is not confirmed.
What
Claude 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.
Why
The 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.
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubt
What, if anything, this changes in the permission prompts a user sees is not confirmed.