Cursor Agents absolutely UNUSABLE when SSHing into Windows Server

[deadinside]

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Cursor Agents run commands to edit files / code, are a lot more prone to errors and that is catastrophic since they use powershell commands and other stupid methods to edit files, the experience is 1% of what it is when editing code that lives on your host machine.

There is no guide to make this works and the agent just literally tries whatever and hallucinates. TRhings that arent

Steps to Reproduce

SSH into any windows server

Expected Behavior

The Agent doesn’t use Powershell to apply modifications to your code, and the changes are ACTUALLY tracked.

Screenshots / Screen Recordings

Operating System

Windows 10/11

Version Information

Latest Cursor Version

For AI issues: which model did you use?

Opus 4.6 Max mode
Composer 2 Fast Max mode

Does this stop you from using Cursor

Yes - Cursor is unusable

[mohitjain (Mohit)]

Hey @deadinside,

This is a known issue with SSH connections to Windows hosts.

A fix for this has been shipped and should be available in the next Cursor update. Please update Cursor when the new version becomes available, and the agent should use its native file tools again instead of falling back to terminal commands.

In the meantime, you can work around this by adding a Cursor rule (in .cursor/rules) that tells the agent to use PowerShell’s Set-Content and Get-Content for file operations instead of Python. Other users have had success with this approach – see this thread for the full workaround.