I have the same issue in 1.4.5 and no early access to 1.4.6 as an enterprise user. When do you release 1.4.6? For me no terminal command ends, and I see “^C” all over the place:
We have more terminal improvements on the version 1.5.0 that is now rolling out to Early Access users.
If you notice the issue still there as well check if there are any common cases when it hangs. e.g. on specific commands, if they are interactive or not, long or short output, or other details you notice.
I have version 1.5.1 and the problem has gotten way worse, now it’s hanging after like 3-8 terminal commands
@enzojx Could you post a Request ID with privacy disabled so we can look into the details? Cursor – Getting a Request ID
66c93ebf-620c-4c1a-b4f3-dae2b86b198f , not sure how do I get the privacy mode disabled as we run in Legacy mode - can I do it somehow for this chat request only or ?
Privacy can be set in Settings > General > Privacy > Privacy Mode. You can turn off privacy for one request and then turn it back on.
As long as privacy is enabled we are unable to look into the request details.
Yeah I think I cant do that since we are on enterprise team license and that setting is controlled by the admin. So there is no way to turn it on for specific request id as individual user?
@enzojx As team settings are controlled by team there can’t be exceptions. We are already looking into additional reports.
Which Cursor version do you use and which OS?
For me on Windows, every terminal command started getting struck after having completed successfully (Cursor stopped being able to automatically realize that it was done) - but if I hit Enter in the Terminal at that point, Cursor will wake up and continue.
Update: Cursor later seemingly lost access to be able to see what’s in the terminal. I told it about it, and it then ran ‘pwd’ in it - after which it regained access and now the issue seems fixed for now.
atm I have
Cursor 1.5.4, vscode 1.99.3
Windows 11, but running inside wsl2 ubuntu 24.04.3 , and then inside devcontainer which is Microsoft Artifact Registry
I’ve noticed that the problem is more prone to happen when there is longer output in terminal, like for example it tries to run test that will output lot of lines, but not the only problem. it sometimes stucks after running simple commands too that output only few lines
This fixed it for me
Here to say also having this problem. What’s the ETA on a fix? This seems like a pretty critical problem to have been open for as long as it has been.
Any chance of an official response? It’s been nearly 6 months, and I’m very tired of having to babysit agent mode and intervene every 30 seconds.
@tylercasper Yes we reworked the terminal integration and its going out early next week as Cursor 1.6.
I’m on windows 11, cursor 1.5.11 with WSL. This happens to me and I couldn’t find a fix yet. I tried ctrl-c, enter, pwd and everything but in the end I have to “skip” and cursor just skips and ignores the run. Very annoying indeed.
Also, I expect it to run in the inline terminal within the chat but it switches to the other terminal under the code for some commands. I don’t understand what happens there. It probably runs one command inline and then it switches to run in the terminal booted from the first command and I don’t see any more output unless I click “show terminal”.
Fix Cursor Terminal Hang on Windows (PowerShell)
Problem
Cursor’s Agent Mode can hang after running commands in the terminal on Windows. This happens because the PowerShell prompt may be too complex for Cursor to detect command completion.
We’ll fix it by creating a minimal prompt for PowerShell that Cursor can handle.
Steps
Open your PowerShell profile
-
Open PowerShell.
-
Run the following command to open your profile in Notepad:
notepad $PROFILE
-
If the file does not exist, Notepad will ask you to create it → click Yes.
-
The profile file will open for editing.
Add a minimal prompt
Paste the following code into your profile:
# Minimal prompt for Cursor
function Prompt {
"PS> "
}
-
This sets a simple prompt (
PS>) without complex themes, glyphs, or Git status. -
Cursor will now correctly detect when commands finish.
Save and close
- In Notepad → File → Save → Close.
Restart PowerShell in Cursor
-
Close the terminal in Cursor and reopen it.
-
You should see the new simple prompt:
PS>
Now Cursor Agent Mode should no longer hang after running commands.
Optional
You can keep a simple prompt in Cursor but still have a fancy prompt in regular PowerShell by detecting Cursor’s environment using $env:TERM_PROGRAM (advanced setup).
If you want, I can also write that optional setup so your normal PowerShell keeps a nice prompt while Cursor gets the minimal one.
The version 1.6.21 fixed the terminal problems for good on my side. Thanks Cursor!
Still broken in latest cursor build. Gets stuck when trying to read git log/ git show etc. Have to pop open terminal and hit ‘q’ to get it unstuck. Plz prioritize fix.
I’m having a consistently bad experience with Cursor 1.6.27 and several other past versions when working with dotnet and having the agent execute commands. It’s unusable, honestly. Windows 11 24H2 (26100.6584) and Powershell 5.1.26100.6584. I wonder if this will ever get fixed properly someday. It’s getting tiring to deal with this bug for so long now. I have to spam enter for newlines to “wake up” the agent so it notices that the command finished.
EDIT: Downloaded PowerShell 7.5.3, will thoroughly test to see if problem is solved, and report back.