Should You Flip CLAUDE_CODE_USE_POWERSHELL_TOOL=1? — A Practical Decision Guide for Windows Developers
When you run Claude Code on Windows, you eventually wonder whether CLAUDE_CODE_USE_POWERSHELL_TOOL=1 is worth flipping on. After running both modes across several projects, here is the decision rubric I now use.
When Bash Misbehaves in Claude Code on Windows — A Practical Note on CLAUDE_CODE_USE_POWERSHELL_TOOL=1
On Windows, Claude Code's Bash-based shell tool sometimes fails in odd ways. Setting CLAUDE_CODE_USE_POWERSHELL_TOOL=1 routes commands through PowerShell and removes many of the symptoms. Here are the practical trade-offs I've seen after living with the switch.
Claude Code's PowerShell Tool — Native Windows, No WSL
The one setting that actually enables the Claude Code PowerShell tool, why auto mode's new default leaves Windows users still approving prompts, and what August's three permission changes left standing. With WSL2 trade-offs and unattended-run safety gates.
Using Claude Code on Windows — Native vs WSL2
Set up Claude Code on Windows using the native installer or WSL2. Includes step-by-step instructions, a practical comparison, and troubleshooting tips.
Cowork 2026 Updates — Windows Support, Scheduled Tasks & New Connectors
A roundup of Cowork's latest features in 2026: Windows support, scheduled tasks, plugin marketplace, new MCP connectors, and more.