Hey, thanks for the detailed report and for the timing screenshot. It shows about 0.3 s for the command itself versus about 12 to 13 s wall time.
This is a known issue on our side. On Windows, the agent can take a long time to detect that a shell command has finished, even though the output is already ready. It shows up most often on Windows build 10.0.26200 with PowerShell 7. We’re tracking the bug, but I can’t give a solid ETA for a fix yet.
Things to try, roughly in order of impact:
Add Cursor to your antivirus or EDR exclusions. On Windows, each agent command spawns a separate process and writes temp files. If AV or EDR scans those, the delay can grow a lot. For the delay case (not missing output), this is usually the biggest lever.
Legacy Terminal Tool: Settings → Agents → Inline Editing & Terminal → enable Legacy Terminal Tool, then fully restart Cursor (not Reload Window) and start a new chat. On some Windows builds this removes the delay completely. If you already tried it and it made no difference, let me know, that’s useful for debugging.
Use Git Bash instead of PowerShell or cmd (via Git for Windows). Reports say it’s more stable than both.
Set Command Prompt as the default profile: terminal.integrated.defaultProfile.windows: "Command Prompt". This can partially improve things on some machines.
Manually click Cancel when it’s stuck on running even though the output is already there. It usually unblocks right away. This isn’t a fix, just a workaround.
Let me know which option helped (or didn’t), especially what you see with Legacy Terminal Tool. When I have an update on the fix, I’ll post it here.
I tried Legacy Tool and also changing the Shell Profile but both did not helped. I think also when changing the Shell Profile it doesn get applied because Cursor still uses Powershell and it says that’s a Bug in Cursor.
Thanks for following up with the results. The fact that Legacy Terminal Tool didn’t make a difference is a useful data point.
A couple things you haven’t tried yet that usually have the biggest impact specifically for latency, not missing output:
AV or EDR exclusions: add Cursor to your antivirus or EDR exclusions. On Windows, each agent command starts a separate process and writes temp files. If your security tool scans those, latency can increase a lot. This is the most likely lever in your case.
Git Bash via Git for Windows instead of PowerShell or cmd. Based on feedback, it’s more stable than both.
About the profile not applying and Cursor still launching PowerShell: after changing terminal.integrated.defaultProfile.windows, you need to fully quit and restart Cursor, specifically Quit, not Reload Window, and start a new chat. Otherwise the agent will keep using the old session. Can you confirm you did a full restart? If you did and it still ignores the profile, it looks like separate behavior that’s been reported here: Agent command execution uses WSL instead of the Windows default integrated terminal (Git Bash)
The latency bug is known on our side and we’re tracking it. I can’t give a solid ETA for a fix yet. Let me know if the AV or EDR exclusions helped, that’s the main question right now.
