Run Command often freezes
Run Command
Execute command normally
Windows 10/11
Version:1.3.3
Commit:1.99.3
No - Cursor works, but with this issue
Hello, this is my exactly problem. Waiting to hear from anyone that can help us.
hi @lili @Paulo_Fraga thank you for the feedback and detailed bug report, we are looking into further improvements and bug fixes on such cases.
Could you please clarify what “freezes” means in this case?
Does Terminal or Cursor freeze? or is this about the Agent not continuing after terminal CLI command exits?
Hello, the command just not continue.
The system Cursor still works normally.
What I’m doing is writing a new prompt trying to explain what’s happening…
Sometimes it works and the flow continues, but I need to do this…
One thing that works for me was ask Cursor to write the commands always for powershell and also in the same command navigate to the correct directory and run it.
I’m testing now this approach.
Regards.
Paulo Fraga.
Great, thank you for the additional info!
I have encountered this problem many times: the cursor cannot get the results of the terminal operation. I must click the skip button to get the results of the terminal operation and automatically continue to generate code for me. If there are results, I must click skip to get them. I cannot get them directly. This problem exists in the latest minor versions, including the current 1.2.4.
I’m having the same issue
it runs a few commands just fine, and then suddenly gets stuck on one of them.
I end up clicking “Skip” over and over again.
I noticed that sometimes you need to open the terminal and check what’s going on occasionally it requires manual intervention.
But a lot of the time, it’s just frozen for no reason.
2 posts were split to a new topic: Terminal stuck in Agent mode
We know that 1.2.4 has that issue which is why we have release several adjustments to improve it. At the moment we are adding more improvements in the 1.3 pre-release and will publish it as stable with those changes.
I have frequent problems with terminal commands being run and then just hanging there until I hit skip and then the chat continues.
When I hit Skip, I then get:
E:\>q^D^C
'q' is not recognized as an internal or external command, operable program or batch file.
I’m on Windows 11 and my terminal is Powershell.
Version: 1.2.4 (user setup)
VSCode Version: 1.99.3
Commit: a8e95743c5268be73767c46944a71f4465d05c90
Date: 2025-07-10T17:09:01.383Z
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
I checked, and it seems to be fixed — it almost never freezes on me anymore.
But… there’s still an issue:
Many times the terminal asks a question — for example, it requests input like Y or N — and then it just hangs for a long time.
If you don’t manually ask it to show the terminal, you have no idea why it’s stuck.
Git commit/push/add Taking TONS of time
Cursor works just fine, but when Doing that Git stuff, it just Takes an agonizing Amount of time, if at all
Solution 
solution to the problem : switching terminal from zsh to bash in VS Code Settings (not “Cursor Settings”) fixes the problem
How to
IN CURSOR
Click (Ctrl + Shift + P)
Type: Terminal: Select Default Profile
Select: bash
Just Make it Do stuff with git
Windows 10/11
Version 1.3.9
VSCode Version : 1.102.3
No - Cursor works, but with this issue
With either shell add this Cursor rule:
When using automated tools to execute git commands, always use git status --porcelain instead of git status for checking repository status. This provides more reliable and faster execution with machine-readable output format that avoids hanging issues.
I’m in Japan, and ever since I updated Cursor to the latest version, I haven’t been able to use the right-hand agent window — it just “blinks” but nothing happens when I try to run a command.
I contacted support by email, but all I get are basic questions, and in the end, they just say they’ll forward it to the responsible team — basically, a waste of time.
I’m a paying user, but honestly, it feels like there’s no difference between paying and using it for free.
Perguntar ao ChatGPT
All it takes is sending a command to the agent — but even that doesn’t work.
I expect the agent to receive the code and execute it — that’s the bare minimum.
Windows 10/11
Versão: 1.3.8 (user setup)
Confirmar: 1.99.3
Data: a1fa6fc7d2c2f520293aad84aaa38d091dee6fe0
Electron: 2025-07-31T21:46:17.109Z
ElectronBuildId: 34.5.1
Chromium: undefined
Node.js: 132.0.6834.210
V8: 20.19.0
SO: 13.2.152.41-electron.0
no
Yes - Cursor is unusable
The agents often get stuck when running commands, even when the command completes successfully. This creates a problem where we have to sometimes shift to terminal, shift+skip or send a new command which cancels the command. This sends the incorrect context to the agent. PLEASE give us a button or function to help the agent move forward when stuck waiting on the command like, ‘command completed’ or something. Thank you.
Just run enough commands in Cursor and it will happen. I am running Windows 11 on a laptop.
What should happen is that after the command is finished running, the agent moves on, but it often does not.
Windows 10/11
Version: 1.3.7 (user setup)
VSCode Version: 1.99.3
Commit: 5d56108ff2401c28f239aa2a527ef424ce7719a0
Date: 2025-07-31T04:16:31.276Z
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
No - Cursor works, but with this issue
Every time Cursor opens a terminal and runs a command, it just hangs after running the command and requires manual intervention to exit, close, or skip (which never works) the terminal so the conversation can continue.
Use Cursor.
Windows 10/11
Version: 1.3.9 (user setup)
VSCode Version: 1.99.3
Commit: 54c27320fab08c9f5dd5873f07fca101f7a3e070
Date: 2025-08-01T20:19:30.453Z
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
Sometimes - I can sometimes use Cursor
Hey, thanks for the report. Could you please specify which terminal shell you are using in Cursor by default?
