Bug Report: Cursor AI Incorrectly Uses "&&" Instead of ";" for PowerShell Command Chaining in Yolo Mode

Bug Reports
1

Description

I’m experiencing an issue when developing code with Cursor AI in Yolo mode. When navigating between project folders and executing multiple commands in PowerShell, the agent consistently uses the “&&” separator for command chaining, which is incorrect syntax for PowerShell. The proper separator for PowerShell is the semicolon (“;”).

Details:

  • This occurs specifically when using agent functionality in Yolo mode
  • Even after specifying the correct syntax in Cursor rules and prompts, the agent reverts to using “&&” after a few interactions
  • My system: Windows 10
  • Impact: This creates unnecessary API calls and consumes credits when commands fail and need to be retried
  • Additional concern: Creates unnecessary load on both Cursor and Claude servers

Suggested Improvement:

If possible, implement a fix at the Cursor level to automatically convert “&&” to “;” when chaining PowerShell commands on Windows systems.

This issue not only affects user productivity but also results in inefficient resource utilization for both users and servers.

3 Likes
2

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.