[DOCS] PowerShell tool docs do not mention supported Windows PowerShell 7 discovery sources

Open 💬 3 comments Opened May 1, 2026 by coygeek

Documentation Type

Missing documentation (feature not documented)

Documentation Location

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

Section/Topic

"PowerShell tool" / "Enable the PowerShell tool"

Current Documentation

The PowerShell tool documentation currently says:

On Windows, Claude Code auto-detects pwsh.exe for PowerShell 7+ with a fallback to powershell.exe for PowerShell 5.1. The Bash tool remains registered alongside the PowerShell tool, so you may need to ask Claude to use PowerShell.

The setup page also says:

Git for Windows is recommended on native Windows so Claude Code can use the Bash tool. If Git for Windows is not installed, Claude Code uses PowerShell as the shell tool instead. WSL setups do not need Git for Windows.

What's Wrong or Missing?

The docs state that Claude Code auto-detects pwsh.exe on Windows, but they do not explain which PowerShell 7 installation sources are detected.

The v2.1.126 release notes say Windows PowerShell 7 installed through the Microsoft Store, MSI without PATH, or the .NET global tool is now detected. That is useful operational guidance for Windows users because these install methods may not expose pwsh.exe through the same PATH-based lookup users expect.

Without this detail, users may incorrectly assume PowerShell 7 must be manually added to PATH or that a Microsoft Store / MSI / .NET global tool installation is unsupported when Claude Code can now detect it.

Suggested Improvement

Add one sentence to the Windows PowerShell detection paragraph, for example:

On Windows, Claude Code auto-detects pwsh.exe for PowerShell 7+ with a fallback to powershell.exe for PowerShell 5.1. PowerShell 7 installations from the Microsoft Store, MSI installers even when pwsh.exe is not on PATH, and the .NET global tool install are detected. The Bash tool remains registered alongside the PowerShell tool, so you may need to ask Claude to use PowerShell.

Optionally add the same detail to the Windows setup or install troubleshooting page where users are choosing between Git for Windows and PowerShell.

Impact

Medium - Makes feature difficult to understand

Additional Context

Affected Pages:

| Page | Line(s) | Context |
|------|---------|---------|
| https://code.claude.com/docs/en/tools-reference | PowerShell tool / Enable the PowerShell tool | Primary PowerShell tool availability and detection documentation |
| https://code.claude.com/docs/en/setup | Set up on Windows | Windows setup path says Claude Code uses PowerShell when Git for Windows is absent |
| https://code.claude.com/docs/en/troubleshoot-install | Claude Code on Windows requires either Git for Windows (for bash) or PowerShell | Troubleshooting page tells users to install PowerShell 7 but does not mention supported detection sources |
| https://code.claude.com/docs/en/hooks | Windows PowerShell tool | Hook-specific PowerShell section repeats that Claude Code auto-detects pwsh.exe |

Version context: v2.1.126 added detection for PowerShell 7 installed via the Microsoft Store, MSI without PATH, or .NET global tool.

View original on GitHub ↗

This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗