[DOCS] Permission docs omit PowerShell auto-approval behavior

Documentation Type

Missing documentation (feature not documented)

Documentation Location

https://code.claude.com/docs/en/permission-modes

Section/Topic

acceptEdits mode and PowerShell command approval behavior

Current Documentation

The docs currently say:

acceptEdits mode auto-approves common filesystem Bash commands: mkdir, touch, rm, rmdir, mv, cp, and sed. These commands are also auto-approved when prefixed with safe environment variables such as LANG=C or NO_COLOR=1, or process wrappers such as timeout, nice, or nohup. Like file edits, auto-approval applies only to paths inside your working directory or additionalDirectories. Paths outside that scope, writes to protected paths, and all other Bash commands still prompt.

The permissions reference also documents Bash-specific matching behavior but no PowerShell equivalent:

### Bash Bash permission rules support wildcard matching with *. Wildcards can appear at any position in the command, including at the beginning, middle, or end:

The PowerShell tool page documents setup and limits, but not permission-mode parity:

The PowerShell tool has the following known limitations during the preview: * Auto mode does not work with the PowerShell tool yet

What's Wrong or Missing?

Changelog v2.1.119 says: PowerShell tool commands can now be auto-approved in permission mode, matching Bash behavior.

The current docs still explain permission-mode auto-approval and permission-rule matching almost entirely in Bash terms. They do not tell Windows users who enable the PowerShell tool whether acceptEdits now auto-approves the same kinds of filesystem commands in PowerShell, whether PowerShell follows the same "Yes, don't ask again" / allow-rule behavior, or how this new parity differs from the still-documented limitation that auto mode does not support the PowerShell tool yet.

Suggested Improvement

Update the permission docs to explicitly document PowerShell parity introduced in v2.1.119:

1. In permission-modes, state that PowerShell tool commands now follow the same permission-mode auto-approval behavior as Bash where applicable.
2. In permissions, add a PowerShell subsection (or an explicit note that Bash matching behavior also applies to PowerShell(...) rules) covering allow/ask/deny patterns and "Yes, don't ask again" behavior.
3. In tools-reference, add a short note linking PowerShell users to the permission docs and clarify that this parity applies to permission modes/rules, while auto mode remains unsupported.

Impact

Medium - Makes feature difficult to understand

Additional Context

Affected Pages:

| Page | Context |
|------|---------|
| https://code.claude.com/docs/en/permission-modes | acceptEdits currently describes auto-approved commands only as "Bash commands" |
| https://code.claude.com/docs/en/permissions | Tool-specific permission rules explain Bash matching and "Yes, don't ask again" behavior, but omit PowerShell parity |
| https://code.claude.com/docs/en/tools-reference | PowerShell tool page documents enablement and preview limitations, but not permission-mode auto-approval behavior |
| https://code.claude.com/docs/en/agent-sdk/permissions | acceptEdits still says other non-filesystem tools are described through Bash-only examples |
| https://code.claude.com/docs/en/agent-sdk/agent-loop | permissionMode table says acceptEdits auto-approves file edits and common filesystem commands, then describes the remaining behavior in Bash-only terms |

Total scope: 5 pages affected

Source: Changelog v2.1.119

Changelog entry: PowerShell tool commands can now be auto-approved in permission mode, matching Bash behavior