Claude Code PowerShell Tool: Native Windows Shell Support (Preview)
Claude CodeClaude Code 2.1.84 introduces an opt-in PowerShell tool for Windows, marking the first time Windows users have access to a native shell tool tailored to their platform rather than relying on Unix-compatible shells. Previously, Windows developers using Claude Code were limited to bash-like environments or WSL workarounds; the PowerShell tool brings Claude's agentic command execution capabilities directly to the native Windows scripting environment. The feature ships as a preview and must be explicitly enabled, with documentation available at the Claude Code docs site.
Sources & Mentions
3 external resources covering this update
PowerShell Tool for Windows (Opt-In Preview)
Claude Code 2.1.84 ships a native PowerShell tool for Windows users — one of the most requested platform expansions since the tool launched. Until now, Windows developers interacting with Claude Code's shell execution capabilities had to rely on Git Bash, WSL, or other Unix-compatible layers. The PowerShell tool changes that by giving Claude direct access to the native Windows scripting environment developers already use for automation, build scripts, deployment pipelines, and system management.
What It Is
The PowerShell tool is an opt-in preview that surfaces PowerShell as a distinct shell execution environment within Claude Code, alongside (not replacing) the existing Bash tool. When enabled, Claude can run PowerShell cmdlets, scripts, and pipelines natively — meaning tasks like interacting with Windows services, managing the registry, invoking .NET APIs, or scripting Azure and Active Directory operations become first-class Claude Code capabilities rather than workarounds.
Why This Matters for Windows Developers
Windows is a major development platform, particularly in enterprise environments, and PowerShell is its dominant scripting language. Agentic AI coding tools that only speak bash have an inherent gap on Windows: they either require WSL (introducing a layer of translation and path friction) or produce commands that don't work natively. The PowerShell tool closes that gap.
For teams building on .NET, Azure, or Windows-native stacks, this means Claude Code can now write and execute platform-appropriate scripts end-to-end — from scaffolding project structure with PowerShell New-Item commands to invoking az CLI pipelines or running dotnet build automation without translation layers.
Preview Status and How to Enable
The feature ships as an opt-in preview, which means it is not enabled by default and requires users to explicitly activate it. This allows Anthropic to gather feedback and refine behavior — particularly around permission prompts, dangerous command detection, and Windows-specific path handling — before promoting the tool to general availability.
Other Notable Changes in 2.1.84
Beyond the PowerShell tool, v2.1.84 includes a number of stability and quality-of-life improvements:
- Claude Code now displays token counts above 1 million in a cleaner format (1.5m instead of 1512.6k), reducing visual noise in long sessions.
- An idle-return prompt nudges users who return after 75+ minutes away to run /clear, preventing unnecessary token re-caching on stale sessions.
- Deep links (claude-cli://) now open in the user's preferred terminal rather than whichever terminal happens to be detected first.
- A range of voice input, scrollback, and keyboard handling fixes round out the release.