Thanks for the report! This exact issue has been fixed in Cursor 1.7!
You’re currently on version 1.5.11, and version 1.7 (released September 29, 2025) specifically addresses PowerShell handling on Windows. From the official changelog:
“On Windows, Agent now correctly uses PowerShell. On macOS and Linux, PowerShell will be used if it’s set as your default shell. Agent also properly detects the shell, preventing Bash-specific syntax errors in PowerShell.”
To fix your issue:
-
Update to Cursor 1.7 or later (Cursor menu → Check for Updates)
-
Once updated, Agents should automatically detect your Windows environment and use PowerShell syntax without needing the manual rule
Let us know if you still see issues after updating to 1.7!