Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix [DOCS] PowerShell tool docs outdated on platform support and enablement [1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#49294•Fetched 2026-04-17 08:45:20
View on GitHub
Comments
0
Participants
1
Timeline
3
Reactions
0
Author
coygeekcoygeek
Participants
coygeekcoygeek
Timeline (top)
labeled ×3
RAW_BUFFERClick to expand / collapse

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:

PageContext
https://code.claude.com/docs/en/tools-referencePrimary 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-varsCLAUDE_CODE_USE_POWERSHELL_TOOL is documented as a Windows-only opt-in preview variable
https://code.claude.com/docs/en/settingsdefaultShell says PowerShell routing is for Windows and points to the PowerShell tool docs
https://code.claude.com/docs/en/skillsSkill frontmatter shell field says PowerShell inline shell commands run on Windows and require the env var
https://code.claude.com/docs/en/slash-commandsSkill frontmatter table repeats the Windows-only PowerShell wording
https://code.claude.com/docs/en/setupWindows 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)

extent analysis

TL;DR

Update the PowerShell tool documentation to reflect the current enablement matrix and supported platforms, including Linux and macOS.

Guidance

  • Review the changelog entry for v2.1.111 to understand the updated behavior of the PowerShell tool.
  • Update the primary PowerShell tool section in the documentation to explain the progressive rollout on Windows and the enablement process on Linux and macOS.
  • Ensure that all linked references, including environment variables and settings documentation, are updated to match the new behavior.
  • Verify that the updated documentation accurately reflects the supported platforms and requirements, including the need for pwsh on PATH on Linux and macOS.

Example

No code snippet is necessary for this issue, as it is related to documentation updates.

Notes

The updates should be applied to all affected pages, which include the primary PowerShell tool section, environment variables, settings, skills, slash commands, and setup documentation.

Recommendation

Apply the suggested content updates to the documentation to ensure accuracy and consistency with the released behavior in v2.1.111. This will help to clarify the enablement process and supported platforms for the PowerShell tool, making it easier for users to understand and use the feature.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#environment variable#request error#file not found#serialization error#model compatibility

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING