[DOCS] PowerShell tool docs outdated on platform support and enablement

Documentation Type

Incorrect/outdated documentation

Documentation Location

https://code.claude.com/docs/en/tools-reference

Section/Topic

PowerShell tool enablement and platform support, plus linked PowerShell shell-selection references

Current Documentation

The docs currently say:

"On Windows, Claude Code can run PowerShell commands natively instead of routing through Git Bash. This is an opt-in preview." "Set CLAUDE_CODE_USE_POWERSHELL_TOOL=1 in your environment or in settings.json:" "* Only supported on native Windows, not WSL"

The environment variable reference also says:

"CLAUDE_CODE_USE_POWERSHELL_TOOL | Set to 1 to enable the PowerShell tool on Windows (opt-in preview). When enabled, Claude can run PowerShell commands natively instead of routing through Git Bash. Only supported on native Windows, not WSL."

Related settings/skill docs also scope PowerShell routing to Windows only, for example:

"Setting \"powershell\" routes interactive ! commands through PowerShell on Windows. Requires CLAUDE_CODE_USE_POWERSHELL_TOOL=1."

What's Wrong or Missing?

Changelog v2.1.111 describes newer behavior:

Windows: PowerShell tool is progressively rolling out. Opt in or out with CLAUDE_CODE_USE_POWERSHELL_TOOL. On Linux and macOS, enable with CLAUDE_CODE_USE_POWERSHELL_TOOL=1 (requires pwsh on PATH)

The current docs still describe the PowerShell tool as Windows-only and opt-in preview behavior. They do not explain:

• that Linux and macOS can enable the PowerShell tool with CLAUDE_CODE_USE_POWERSHELL_TOOL=1
• that pwsh must be available on PATH on Linux and macOS
• that Windows rollout behavior now supports opting in or out with CLAUDE_CODE_USE_POWERSHELL_TOOL

This leaves the primary PowerShell tool documentation and related configuration references inconsistent with the released behavior in v2.1.111.

Suggested Improvement

Update the PowerShell tool docs to describe the current enablement matrix in one authoritative place, then align linked references to match it.

Suggested content update:

• Windows: explain that the PowerShell tool is progressively rolling out and that CLAUDE_CODE_USE_POWERSHELL_TOOL can be used to opt in or opt out
• Linux and macOS: explain that users can enable the PowerShell tool with CLAUDE_CODE_USE_POWERSHELL_TOOL=1 and must have pwsh on PATH
• Remove or revise wording that says the tool is only supported on native Windows when that no longer reflects current behavior
• Update defaultShell / skill shell wording so it does not imply PowerShell routing is Windows-only once the tool is enabled on Linux or macOS

Impact

Medium - Makes feature difficult to understand

Additional Context

Affected Pages:

| Page | Context |
|------|---------|
| https://code.claude.com/docs/en/tools-reference | Primary PowerShell tool section says the tool is Windows-only, describes only Windows opt-in setup, and lists Windows-only support limits |
| https://code.claude.com/docs/en/env-vars | CLAUDE_CODE_USE_POWERSHELL_TOOL is documented as a Windows-only opt-in preview variable |
| https://code.claude.com/docs/en/settings | defaultShell says PowerShell routing is for Windows and points to the PowerShell tool docs |
| https://code.claude.com/docs/en/skills | Skill frontmatter shell field says PowerShell inline shell commands run on Windows and require the env var |
| https://code.claude.com/docs/en/slash-commands | Skill frontmatter table repeats the Windows-only PowerShell wording |
| https://code.claude.com/docs/en/setup | Windows setup section describes native PowerShell as a Windows opt-in preview and links to the outdated tool page |

Total scope: 6 pages affected

Source: Changelog v2.1.111

Exact changelog entry:

Windows: PowerShell tool is progressively rolling out. Opt in or out with CLAUDE_CODE_USE_POWERSHELL_TOOL. On Linux and macOS, enable with CLAUDE_CODE_USE_POWERSHELL_TOOL=1 (requires pwsh on PATH)