Cursor getting stuck in terminal

I’m on the latest v1.2.2 and it still gets caught up and I still have the q^w^c terminal error that breaks the whole conversation.

2 Likes

Yes, the internal cursor cmd often gets stuck with long commands where the pager is getting triggered.

then I often quite the terminal…

I am experiencing the issue on windows, as do probably everyone else. There are some fixes available for iOS people claim it helped them, but this still remains unresolved on windows…

3 Likes

giving this a whirl, thanks for the suggestion

switching to git bash has improved my workflow dramatically. Highly recommend this as a workaround to anyone.

I have been experiengin the same problem as I mentioned before. I have made the effort to completely describe the problem and also related problems on windows.

How do we tell the agent to use Git Bash?

It’s a crappy workaround, but I’m willing to try anything at this point!

You can change default terminal in the settings.
Also if you have one open, you can click the more options arrow and click “Select default profile”
But you have to have git bash installed.

1 Like

I’ve had this problem myself on and off but rarely enough I didn’t bother trying to fix it. However it’s getting bad now, almost every prompt. Often the easy fix is click on the terminal window and press Enter. The moment it sees the shell prompt a 2nd time, it realizes the command is finished.

I’m on Windows, using Powershell as my terminal. As some point I changed Cursor to use a newer (7.5.1) version of Powershell, I think because the older version didn’t have a feature Cursor often tried to use (perhaps pipes or && to execute multiple commands).

Per a comment above, I’ll try changing to the git bash shell instead to see if that will fix it for good.

I did notice just now that Terminal → Integrated → Default Profile: Windows is set to “null” which it says is the default, instead of one of the PowerShell choices.

1 Like

I see this mostly in PowerShell commands. I’ve instructed Cursor to use cmd to run terminal commands and that seems to help, but Cursor forgets that often.

I tried switching to git bash, still having the same issue, only now i hitting enter doesn’t do anything either :worried:

Hi everyone here, the issue is being worked on by Cursor Team.

I think we also have a few duplicate posts on this so the efforts on communicating this properly becomes a bit more tricky.

here are similar cases

2 Likes

I have exactly the same problem.
If I [skip] then that almost always cancels the prompt.
If I [move to background] that mostly recovers & continues.

Press Enter in the Agent terminal if everything went as it should, or Cancel if Enter does not work or the process inside the terminal clearly freezes without ending - this way you will give the correct context for the Agent.

@T1000 I suggest to provide a link to that recommendation if new duplicates appear.

Sure, the goal is to do that, though not yet automated.