Describe the Bug
Since the last update, my cursor AI keeps hanging at open command line prompts after executing something.
Steps to Reproduce
Impossible to reproduce at 100%. But asking it to make a complex task involving command lines, and watching as one of the tries hangs indefinitely
Expected Behavior
It’s meant to detect that powershell gave back control and continue with the next “thought” or tool call
Operating System
Windows 10/11
Current Cursor Version (Menu → About Cursor → Copy)
Version: 1.2.1 (user setup)
VSCode Version: 1.99.3
Commit: 031e7e0ff1e2eda9c1a0f5df67d44053b059c5d0
Date: 2025-07-03T06:16:02.610Z
Electron: 34.5.1
Chromium: 132.0.6834.210
Node.js: 20.19.0
V8: 13.2.152.41-electron.0
OS: Windows_NT x64 10.0.26100
Additional Information
Using claude sonnet 4
Does this stop you from using Cursor
Yes - Cursor is unusable
1 Like
it seems like this happens when the powershell command executes so fast that cursor doesn’t have time to catch it. entering manually in the command line and replaying the last command seems to make cursor aware that it’s finished
Nobody is having the issue besides me ?
Yes, i’m currently using ctrl c or pressing enter or even replaying the previous command but it requires manual intervention which i would like to avoid.
as for the zsh command, i don’t see how it’s related adn some say it was solved in the latest release but it doesn’t seem to be solved on my side
o3 tells me that the issue is introduced by 1.2.1 and that the shell integration is glitchy
it suggests removing the psreadline module but no lucking getting that to work even after the module removed
it also suggests enabling shell integration in the vs code features but this didn’t work also
I think one issue with that is that PSReadLine is actually built-in to PowerShell so it’s hard to remove (need to remove it manually from disk I think).
Are you using any terminal themes like Oh My Posh? That seems to be causing some issues for me but I added
Exiting profile early due to Cursor Agent
if ($env:PAGER -eq ‘head -n 10000 | cat’ -or $env:COMPOSER_NO_INTERACTION -eq ‘1’)
{
return
}
To my $PROFILE to try and circumvent that issue.