Run Command often freezes

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Can you guys finally fix the issue when the terminal hangs?

Steps to Reproduce

LLM (e.g. sonnet4 or sonnet4 thinking) tries to run any terminal command and hangs forever.

Screenshots / Screen Recordings

Operating System

Linux

Current Cursor Version (Menu → About Cursor → Copy)

Version: 1.4.5
VSCode Version: 1.99.3
Commit: af58d92614edb1f72bdd756615d131bf8dfa5290
Date: 2025-08-13T02:08:56.371Z
Electron: 34.5.8
Chromium: 132.0.6834.210
Node.js: 20.19.1
V8: 13.2.152.41-electron.0
OS: Linux x64 6.14.0-28-generic

Does this stop you from using Cursor

Yes - Cursor is unusable

Hey, thanks for the report here!

We’ve been working hard on the reliably of terminal command execution recently, and I’ve passed this to the team to look into - I’d expect significant improvements here in our upcoming version.

1 Like

Here for my weekly complaint on cursor agent and terminal bugs. Really hoping you guys finally figure this out for 1.6 as it renders cursor useless for any semi-complex work.

Version: 1.5.11 (user setup)
VSCode Version: 1.99.3
Commit: 2f2737de9aa376933d975ae30290447c910fdf40
Date: 2025-09-05T03:48:32.332Z
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.19045

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

I am working on Windows in WSL terminal with Python venv or docker/docker compose.

Cursor agent (any model) in 50% of the cases cannot recognize the completion of command it is executing via terminal. For example:

```

ubuntu@user:/path/$ docker compose ps
results

ubuntu@user:/path/$
```

At this point the agent is stuck still waiting for a response…
Clicking on skip sometimes helps (after a few times), but many times it is just trying to run the same command again.

It feels like the agent is unable to recognize the command line.

Most of the times it is trying to cd into project internal directory, even though it is already in this directory.

Steps to Reproduce

Any request involving execution of multiple cli commands gets stuck

Expected Behavior

Recognize that a simple immediate command ends, when cli prompt appears.

Operating System

Windows 10/11

Current Cursor Version (Menu → About Cursor → Copy)

Version: 1.4.5 (system setup)
VSCode Version: 1.99.3
Commit: af58d92614edb1f72bdd756615d131bf8dfa5290
Date: 2025-08-13T02:08:56.371Z
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.22631

Does this stop you from using Cursor

Sometimes - I can sometimes use Cursor

How do I permanently tell Cursor to stop running foreground commands that stall the chat, and use the text tools instead? It persists in using foreground commands that never complete, such as: “chmod +x scripts/troubleshoot-production.sh”

Is there something I need to put in a cursor rule or change a setting? This is maddening behavior. I have to cancel all these commands and can never prompt cursor to run the text tools instead.

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

I’ve got an issue where the terminal fails to return control to the cursor agent when the agent runs the terminal inline. Sometimes the terminal will run just fine, and then return control to the agent, so it can proceed.. but sometimes the terminal just sits there, at the command line, with its task complete, but yet not returning control back to cursor.

I have to go into the terminal window inline, and press enter, once, or twice or sometimes more, before it returns control to the agent.

Also, sometimes when I have to do this, it blanks out the terminal window just as its returning control, so cursor agent complains that the terminal command produced no output. But that’s not the case. It did… but then it was blanked.

This is frustrating because I rely on the agent running terminal commands, and then interpreting the results from those commands. And, it forces me to sit and hand hold the agent running, because I have to occasionally press enter to make the agent proceed.

Steps to Reproduce

  1. Ask the agent something that would make it produce a terminal and run a command. Something like a database query, or a directory scan.
  2. The agent will complete the command, and return to the command line in the terminal.
  3. The terminal will sit there, not proceeding automatically, until the user presses enter within the terminal, causing the command line to show again, and again,

so I’ll see the terminal say:

PS C:\repos\myProject> _

I press enter a few times

PS C:\repos\myProject> 
PS C:\repos\myProject> 
PS C:\repos\myProject> _

before it returns control to the agent. If I happen to not be sitting there, the agent will just wait forever.

Expected Behavior

When a terminal completes execution, it should immediately return control to the agent, passing along the textual output generated in the terminal.

I’m using powershell.

Operating System

Windows 10/11

Current Cursor Version (Menu → About Cursor → Copy)

Version: 1.5.11 (user setup)
VSCode Version: 1.99.3
Commit: 2f2737de9aa376933d975ae30290447c910fdf40
Date: 2025-09-05T03:48:32.332Z
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

For AI issues: which model did you use?

claude-4-sonnet, thinking, Max

For AI issues: add Request ID with privacy disabled

9427180a-0cdc-4c6f-a036-e894d06a2280

Does this stop you from using Cursor

Sometimes - I can sometimes use Cursor

1 Like

1.6.27 still freezes the command line, and I don’t know which version will actually fix it

Version: 1.6.35 (user setup)
Commit: 1.99.3
Date: b753cece5c67c47cb5637199a5a5de2b7100c180
Electron: 2025-09-19T17:40:36.856Z
ElectronBuildId: 34.5.8
Chromium: undefined
Node.js: 132.0.6834.210
V8: 20.19.1
OS: 13.2.152.41-electron.0

1.6.35 still freezes the command line

I have the same exact issue. It happens on both IDE and CLI, but only when I’m using Coder. If I’m running locally (macOS), it doesn’t happen. Interestingly enough, nobody in the company is experiencing the same issue. It just stops the agent, and the command does not run.

Update: I downgraded version 1.6 to 1.5 and it got to work. Then it updated automatically and continued to work. Let’s see if it going to stop again.

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Hey, cursor constant fails at PSQL commands.

the first command opens psql in the terminal, cursor tries ^C to close it - this fails as PSQL doesn’t have that command. then the subsequent commands into terminal fail.

Been an issue since early days - hoping for a bug fix or workaround - how else are people reading tables?

Steps to Reproduce

ask psql to look into your table

Expected Behavior

will just hang the agent

Operating System

Windows 10/11

Current Cursor Version (Menu → About Cursor → Copy)

Version: 1.5.11 (user setup)
VSCode Version: 1.99.3
Commit: 2f2737de9aa376933d975ae30290447c910fdf40
Date: 2025-09-05T03:48:32.332Z
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.22631

For AI issues: which model did you use?

grok code

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

stuck at running command on terminal

Steps to Reproduce

ask it to run and check latest changes from git

Screenshots / Screen Recordings

Operating System

Windows 10/11

Current Cursor Version (Menu → About Cursor → Copy)

Version: 1.6.45 (user setup)
VSCode Version: 1.99.3
Commit: 3ccce8f55d8cca49f6d28b491a844c699b8719a0
Date: 2025-09-22T18:22:38.013Z
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

Yes - Cursor is unusable

+1 to bump the thread - same as @Muhd_Ridhwan

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Regardless of the command, Cursor gets stuck waiting in terminal.
Even if the command finished and returned the correct exit codes.

It hangs on:

  • cd directory/
  • npm tests
  • pip installs
  • docker builds
  • git commands

Windows 11, this has been happening for the past >5 released versions.

Steps to Reproduce

Install Cursor IDE on Windows 11.
Ask it to complete any task that would require a command line call → It gets stuck

Expected Behavior

… Don’t get ■■■■?

Operating System

Windows 10/11

Current Cursor Version (Menu → About Cursor → Copy)

Version: 1.7.11 (user setup)
VSCode Version: 1.99.3
Commit: 867f14c797c14c23a187097ea179bc97d215a7c0
Date: 2025-09-26T16:55:04.318Z
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

Yes - Cursor is unusable

Hey, thanks for the info. The team is working on a fix.

The new version should have solved this problem, but the default command terminal execution efficiency is much slower than PowerShell. It is about 2 seconds slower at the beginning of execution, and about 1 second slower in the middle of execution than PowerShell. I hope it can be improved.

Any timeline we can expect?

Where does the bug appear (feature/product)?

Cursor CLI

Describe the Bug

When Cursor AI tries to run cli commands, suddenly gets stuck and the process continues infinitely, so I have to stop the process forcely and give the instruction to re-run, this happen sometimes recurring (~3 out of 5), I don’t know if either Cursor CLI suddenly disconnects from the external window or it’s related to To-dos list or long chats or something else, but it’s something a bit annoying. I’ve been installing the latest IDE versions but the issue continues happening.

I opted to open the command in external window (as you can see in the attached image) and I confirmed that the command had finished and I need Cursor checks for errors to help to analyze and solve but I had to stop the command and re-instruct it. It looks like Cursor get disconnected from the CLI.

Steps to Reproduce

instruct cursor AI to build a project or full solution several times.
check when it gets stuck
open external windows to validate if commands finished and check if the process got stuck.

Expected Behavior

cli command should communicate with cursor properly.

Screenshots / Screen Recordings

Operating System

Windows 10/11

Current Cursor Version (Menu → About Cursor → Copy)

Version: 1.7.33
VSCode version: 1.99.3

For AI issues: which model did you use?

Agent - Auto

Does this stop you from using Cursor

No - Cursor works, but with this issue

Hello, is this problem solved?

This still happens to me on a regular basis when I’m running in legacy terminal mode. I have to run in legacy terminal because read-only agent terminals are a terrible idea.

This still happens on windows in

Version: 2.1.39 (user setup)
VSCode Version: 1.105.1
Commit: 60d42bed27e5775c43ec0428d8c653c49e58e260
Date: 2025-11-27T02:30:49.286Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Windows_NT x64 10.0.26200

It got better for a while, and now it’s back.