Run Command often freezes

Describe the Bug

When executing shell command (powershell) Cursor hangs until user presses (multiple) enter on embedded command line.

Steps to Reproduce

  1. Make Cursor run powershell command
  2. Wait for command prompt to re-appear
  3. Cursor hangs on spinning icon next to Shift+Skip

Expected Behavior

Cursor should continue working

Operating System

Windows 10/11

Current Cursor Version (Menu → About Cursor → Copy)

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

Does this stop you from using Cursor

No - Cursor works, but with this issue

Hey, I noticed that you’re using version 1.3.9, while the latest version is 1.4.3, in which we’ve fixed many bugs, including the one you mentioned. Try updating.

Alas, I am on 1.5.5 now and still experience this error. very frustrating.

1.5.5 still shows the same bug. Windows/Powershell - pressing enter in the embedded terminal until the little dots start dancing, or popping out the terminal seems to unlodge it.

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

I am not sure why my Cursor updated, I did not ask it to, however I find myself on v1.5.5 and to my great dismay, this has now introduced a CRITICAL terminal stalling issue. The terminal stalls constantly. Very occasionally, the agent will automatically continue past a stall, howeever the vast, vast majority of the time it will not continue. I have tried to prompt the agent and llm to see i they can resolve this issue on their own, and they simply cannot. I often run complex, long-running requests these days, and this has had a devastating impact on my ability to get work done, since the agent seems to rely on terminal commands for almost everything (even though many of these operations have built-in native commands, like moving files around, copying files, grepping, linting, etc.)

This is very much a show-stopping bug, as when I have to manually prompt for the agent to continue, it seems to reduce the stability of that chat, and the agent much more quickly starts having problems following the rules and requirements of my original prompt, than if the prompt is allowed to run continuously on its own without interruptions.

Steps to Reproduce

Craft a prompt that would involve a terminal command.
Wait for terminal command.
Terminal command stalls.
Weep.

Expected Behavior

Terminal commands function as they always have before: They run, the agent recognizes command completion (status code/return code), and acts accordingly.

Operating System

MacOS

Current Cursor Version (Menu → About Cursor → Copy)

Version: 1.5.5 (Universal)
VSCode Version: 1.99.3
Commit: 823f58d4f60b795a6aefb9955933f3a2f0331d70
Date: 2025-08-25T17:40:25.290Z
Electron: 34.5.8
Chromium: 132.0.6834.210
Node.js: 20.19.1
V8: 13.2.152.41-electron.0
OS: Darwin arm64 24.5.0

Does this stop you from using Cursor

Sometimes - I can sometimes use Cursor

Seems something has changed with the way the agent detects terminal command completion. I’ve been fiddling around with this for a while now, as it is completely devastating my workflow. Things were fine when I was on 1.4.5, not long ago I was upgraded to 1.5.5 (Cursor hung earlier today, after pushing my M4 so hard it sounded like a jet engine, NEVER heard that with an M1-4 before!) I suspect when I restarted after that crash, I was hit with an automatic update (which really bothers me! I have been following the 1.5.x thread and the news has not been good about its stability, and I DO NOT want to be on 1.5 right now!)

What I have discovered here, after opening the agent’s terminal instance and fiddling with it, is that the Agent WILL NOT continue after issuing a terminal command, until I, the user, go into teh terminal instance, and hit the return key. This creates a new prompt line in the terminal, and I am not sure if it also issues some kind of status code/result code again. In any case, manually hitting return in the agent’s terminal instance, will get the agent moving again.

Of course, the next terminal command the agent runs, results in the agent hanging AGAIN, so the user has to hit enter manually after every single command the agent runs.

This really needs to be fixed ASAP.

Additionally, @condor or any other Cursor rep…I really cannot be dealing with a new bug today, when it was NOT my choice to update cursor! I need to roll back to 1.4.5, because I need a stable, working agent. I have too much work to do to be bug hunting in 1.5.x.

Alright. This problem has morphed into something even bigger. I am now experiencing repeated PTY Host connection issues. I am not sure why there are so many problems with terminals in Cursor, but I am now starting to see my integrated terminal names in the terminal list turn red, with a disconnected icon. Then a yellow button will appear on the status bar labeled “PTY Host”. I have to click that, and sometimes it will reconnect.

I don’t know what changed in 1.5.x, but it is now causing some crazy, if intermittent, problems. The previous issue with the agent terminal, I was eventually able to resolve (well, I seem to have to resolve it once every new agent chat or tab) by running other commands in the agent’s terminal instance. Eventually it will no longer hang. However every new chat or new tab, then requires me to fiddle around with running commands myself until it works without pausing again.

I am unsure if this PTY Host connection issue, is a part of that problem as well. Sometimes my terminals seem to just stall, can’t type, can’t CMD+C to kill anything, they are just dead, but the PTY Host alert doesn’t appear in the status bar. At least, not right away…eventually I think it will, but sometimes it takes a long time.

Regardless….1.5.5 introduced some severe terminal issues. This is really bad news. very breaking, highly disruptive. Its crashed most of my day here.

I have this problem also

Please fix this constant stopping when it runs tasks . It runs a task then waits far to long then does not go to the next it needs to do and i have to keep pressing enter its virtualy every f task seems to be a terminal thing . suly if me pressing enter makes it move on surly you can make the agent do it automaticly

Every single terminal task hangs - 100% of the time without fail

1 Like

Thank you all for the updates and we will check further for the cause. It is not the expected case but we may ask for more info to help reproduce your cases.

Not even nearly 100% for me, but it happens from time to time for sure. Maybe more like 5-15%?

I have few options I have added to configuration, but I do not know if they are help or not:

{
    "window.commandCenter": true,
    "workbench.colorTheme": "Visual Studio 2019 Dark",
    "cursor.general.disableHttp2": true,
    "terminal.integrated.automationProfile.windows": {
    
  "path": "C:\\Program Files\\PowerShell\\7\\pwsh.exe",
  "args": ["-NoLogo", "-NoProfile"]
},
    "terminal.integrated.defaultProfile.windows": "PowerShell (NoProfile)",
    "terminal.integrated.profiles.windows": {

        "PowerShell (NoProfile)": {
            "source": "PowerShell",
            "args": ["-NoLogo", "-NoProfile"]
          },
        "PowerShell": {
            "source": "PowerShell",
            "icon": "terminal-powershell"
        },
        "Command Prompt": {
            "path": [
                "${env:windir}\\Sysnative\\cmd.exe",
                "${env:windir}\\System32\\cmd.exe"
            ],
            "args": [],
            "icon": "terminal-cmd"
        },
        "Git Bash": {
            "source": "Git Bash"
        }
    },
    "terminal.integrated.shellIntegration.decorationsEnabled": "never",
    "terminal.integrated.automationShell.windows": "C:\\Program Files\\PowerShell\\7\\pwsh.exe",
"terminal.integrated.enablePersistentSessions": false,
"terminal.integrated.shellIntegration.enabled": false,
"terminal.integrated.suggest.providers": {
    "terminal-suggest": true,
    "pwsh-shell-integration": true
}

}

I also did notice quite often agent was stuck running command “dotnet build”, and it would say in the end that there are updated workloads. I thought maybe the agent is expecting to have the build summary line at the end instead of that, so I updated the workload.

However, many definitely are not using same tools or even OS as I am, so chances are these are no use.

I might also add, that after updating from 1.4.5 to 1.5.x I have seen the terminal for some reason going more often to background. I have not toggled any setting to do that as far as I know. At least once it has gotten stuck there too, but it is more difficult to see.

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Has been happening since I started paying for this product. Things will be running smoothly for a few commands, then all of a sudden, the terminal will just hang and get caught up. No way to get Cursor to progress without skipping (sometimes doesn’t even work) or telling the agent to proceed. Even after telling it to proceed, the problem will continue to occur until you’ve created an entirely new chat, popped out the terminal, and destroyed it, or tried any variation of other random fixes.

Windows 11 Home, have tried using multiple different terminals (currently Git Bash). Why is this so persistent? It completely destroys my workflow.

Steps to Reproduce

Use the product during an SSH session. Wait patiently. Watch your terminal get caught up and hang after a tool use.

Operating System

Windows 10/11

Current Cursor Version (Menu → About Cursor → Copy)

Version: 1.5.7 (user setup)
VSCode Version: 1.99.3
Commit: 6aa7b3af0d578b9a3aa3ab443571e1a51ebb4e80
Date: 2025-08-27T22:43:32.248Z
Electron: 34.5.8
Chromium: 132.0.6834.210
Node.js: 20.19.1
V8: 13.2.152.41-electron.0
OS: Windows_NT x64 10.0.26100

Does this stop you from using Cursor

Sometimes - I can sometimes use Cursor

Just encountered this for the 50th time today. Just hangs.

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

I’ve been using “Cursor on Windows” since early Feb. It crashes more than 50% of the time when doing anything on my box (powershell and/or cmd.exe and/or wsl) - I use 3 different PC’s (Windows 10N laptop, Windows 11home laptop, Windows 11Pro desktop in a VM) and it “reliably” locks up when doing anything on all those machines. I just assumed this would get fixed at some point, but never seems to?

Steps to Reproduce

Get Claude to run any commands on a windows host.

Expected Behavior

I would expect the command to run, and show me the output properly.
What really happens, is it sometimes (usually) runs the commands, always (without fail) screws up showing me the output (all kinds of weird stuff and blank lines and ^C^C^C etc shows at the end every time), and more than 50% of the time it locks up forever at this point.

Operating System

Windows 10/11

Current Cursor Version (Menu → About Cursor → Copy)

Version: 1.5.6 (user setup)
VSCode Version: 1.99.3
Commit: 6eed2e036b92b60f0cef5b52a2e1b99f3358bca0
Date: 2025-08-27T16:29:33.866Z
Electron: 34.5.8
Chromium: 132.0.6834.210
Node.js: 20.19.1
V8: 13.2.152.41-electron.0
OS: Windows_NT x64 10.0.17763

Additional Information

I am interested to learn if other people have this problem as well - is this a known issue, or have I somehow fluked 3 different machines all with some local problems causing this?

Does this stop you from using Cursor

No - Cursor works, but with this issue

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

When chatting with the new grok fast code model, I’m seeing it try to run terminal commands and get stuck. The command it was executing ran, but the chat didn’t see it complete and use the output.

It’s not a consistent thing and other chats will be able to do this same thing without issue for a few runs, then it starts failing and stays that way.

Steps to Reproduce

Chat with the grok model and have it do a few bash script executions like this one at the end of any changes it makes:

#!/usr/bin/env bash
set -exo pipefail

SCRIPT_DIR=$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)
cd "$SCRIPT_DIR"

# Check if SwiftLint is installed
if ! command -v swiftlint &> /dev/null; then
    brew install swiftlint
fi

echo "Running SwiftLint on Sources/..."

# Run SwiftLint on the Sources directory
swiftlint lint Sources/

echo "Linting complete!"

Expected Behavior

It should see the return code and know it’s done.

Screenshots / Screen Recordings

Operating System

MacOS

Current Cursor Version (Menu → About Cursor → Copy)

Version: 1.5.9
VSCode Version: 1.99.3
Commit: de327274300c6f38ec9f4240d11e82c3b0660b20
Date: 2025-08-30T21:02:27.236Z (2 days ago)
Electron: 34.5.8
Chromium: 132.0.6834.210
Node.js: 20.19.1
V8: 13.2.152.41-electron.0
OS: Darwin arm64 24.5.0

Does this stop you from using Cursor

No - Cursor works, but with this issue

Describe the Bug

Every other terminal command, cursor doesnt recognized the command status to continue independently, that means I need to intervene manually ever more, since recent updates. Its time consuming and prevents reasonable task size automation. Annoying, and not response from the team.

Steps to Reproduce

Just give it terminal commands to run like docker logs inspection, netstat, etc.

Expected Behavior

when forking a terminal, fork a watchdog to see when that terminal should have completed its job and checks its status properly

In the picture attached, cursor will never conclude the execution to decide what to do next. And recently this happens every other terminal command.

In just a minute, another one:

Operating System

Windows 10/11

Current Cursor Version (Menu → About Cursor → Copy)

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

Does this stop you from using Cursor

No - Cursor works, but with this issue

I pay them enough to be agitated :slight_smile:

Yes, I completely understand! Deleted my comment priorly.
I’m a new user and still baffled by the new possibilities

I encountered the same problem

2 Likes