the agent runs a command like “ls” in my shell (WSL with legacy console turned ON since otherwise I get powershell due to a bug that cursor can’t fix).
The ls completes instantly, but the agent spins forever waiting for the command to complete. If you hit cancel, the Agent never gets the console output.
This is extremely frustrating and easily my #1 biggest cursor annoyance and this has been happening since I started using cursor 6 months ago.
It appears the workaround is to turn off legacy teminal tool, so that each command must be prefaced with wsl.exe since it is impossible to tell cursor to use wsl directly even with the proper configs. Is that right?
Steps to Reproduce
Windows. Set your interactive shell to WSL. have the agent do any simple command like ls -l. Most of the time (not always) it will spin forever even though the command completes instantly.
Expected Behavior
When the command completes, it should notify Cursor the results of the output.
Operating System
Windows 10/11
Current Cursor Version (Menu → About Cursor → Copy)
My working environment is windows+wsl(ubuntu)+cursor. My dev working space is in WSL and I started cursor with “cursor .” in the project home folder. Recently I updated cursor extensions (WSL/Remote/Dev Container from anysphere) as required. and then cursor agent hangs very frequently when it was running command like “tail -f 20” or “ls” etc. I believe it did not happen once with old extensions from vscode. It is very very annoying. help please…
Good to know I found the best workaround which is to disable the legacy terminal tool which forces powershell and tell cursor to prefix commands with wsl.exe
