Agent doesn't wait for terminal command to finish

Bug Reports
1

Describe the Bug

Cursor Agent doesnt wait for terminal command completion, causing it to either retry, or assume something was wrong, or skipping the command output alltogether.

Occurs since the update yesterday that added the dropdown with run/skip/reject/allowlist that now opens by default under the command before it executes.

Steps to Reproduce

  • Run a longer running command in terminal
  • Cursor Agent continues before it is finished and doesn’t get terminal output

Expected Behavior

  • Cursor Agent waits for terminal command to finish before continuing

Operating System

Linux

Current Cursor Version (Menu → About Cursor → Copy)

Version: 1.3.2
VSCode Version: 1.99.3
Commit: 7db9f9f3f612efbde8f318c1a7951aa0926fc1d0
Date: 2025-07-24T22:20:09.787Z
Electron: 34.5.1
Chromium: 132.0.6834.210
Node.js: 20.19.0
V8: 13.2.152.41-electron.0
OS: Linux x64 6.15.7-200.fc42.x86_64

Additional Information

Tried ‘Opening in terminal’ when running, but this had similar effect.

Asked Agent to always execute a second command “echo Terminal Ready” after each command and then check the result above the echo message. This seems to work about 50% of the time.

Getting Cursor to recognise the command output and for instance figure out what went wrong with a test is a real pain now.

Does this stop you from using Cursor

Yes - Cursor is unusable

3

Hey, can you confirm if this also happens in a new chat?

4

Hi, yes i can confirm this happens continuously. Also after restarting the IDE, rebooting my machine.

I’ve done some testing and haven’t found an explanation yet. However I do have some interesting observations to share at least…

This worked just fine before yesterday, which made me think maybe this is caused by a change in the commands i run instead of Cursor (predominantly long running dotnet commands).

But testing this with npm in a fresh chat got me the same results:

image
image1535×1567 208 KB

You obviously can’t see the timing but it started responding before the command was finished and it shows it wasn’t able to see the output of the command.

Then, when I manually open a new shell from -within- an existing shell in the Cursor terminal window inside the chat (i.e. typing sh ) and then let cursor issue a new terminal command:

==> Now Cursor keeps waiting indefinitely, never noticing the command it started completes.
==> When I exit the created shell manually by typing exit, Cursor responds as if the command just finished.

So somehow cursor does wait and eventually notices my nested shell exiting, but it didn’t wait for unnested commands like npm or dotnet.

Hope this helps in narrowing down the issue. I’ll happily help debugging it further if needed.

5

Thanks for the additional info, we’ll look into it. Also, could you share the request ID? For this, you need to disable privacy mode if it’s enabled, then reproduce the issue when it happens again and copy the ID.

6

Hi,

I reproduced it in a clean repo with privacymode disabled:

image
image1435×1375 217 KB

In this image the first shell command failed because it used the wrong package name. The second shell command succeeded and installed correctly.

But the 3rd command was issued almost immediately after, and before the second command completed.

I cancelled the 3rd command after which the output of the second command was also no longer visible in the chat terminal window (but the 2nd did complete successfully).

Request ID: 9df8a616-5026-44d7-ac3f-2bfc2e6382b1

Cheers

1 Like