Stuck waiting for terminal completion and Terminal output removed

Bug Reports
1

Describe the Bug

I don’t know if others are experiencing this but it’s quite annoying.

The terminal interface from within the chat area is fantastic. It demonstrates how the AI interacts with the server.

However, I have consistently noticed two distinct issues.

The first is that the terminal output will not be shown. The command is generated, and displayed but the terminal itself and it’s output are not shown. It gives the appearance of hung, but if I get impatient and click the go to background button, it will show that the terminal was actually working. This is both annoying and dangerous.

The second is that the detection that the console has completed is not working. The command will complete, I will wait… and wait and eventually click the skip button which sends the ^c to the terminal. Most times the AI reads the terminal output like normal into it’s context. However, sometimes it “detects” that I cancelled the command.

Steps to Reproduce

I have not found a reliable way to see this happen other than using the application.

I can tell you that the connection is not an issue… this is most certainly a bug of some sort. If that bug is from the VS Code side… I don’t know.

This happens multiple times during daily use and is NOT rare.

I’ll try and grab screenshots the next time it happens.

Expected Behavior

Consistent behavior as it is intended

Operating System

Windows 10/11

Current Cursor Version (Menu → About Cursor → Copy)

Version: 1.1.3 (user setup)
VSCode Version: 1.96.2
Commit: 979ba33804ac150108481c14e0b5cb970bda3260
Date: 2025-06-15T06:55:04.603Z
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

2 Likes
2

Okay, so it seems this is quite common.

The fix ended up installing VS code on the target server. In my case it was a snap module. Not a fan that this is needed since the snap needs to outside itself to be functional (what is the point of having it in snap then!).

Adding this line to my .bashrc check for the terminal being a vscode terminal and running the script fixed it…

[[ "$TERM_PROGRAM" == "vscode" ]] && . "$(code --locate-shell-integration-path bash --user-data-dir='.' --no-sandbox)"

Credit to the forum post that I can’t find anymore :frowning:

If in WSL, remove the --no-sandbox they said.

1 Like
4

UPDATE:
Not solved for the terminal scroll disappearing… so that issue is still there

5

I have the same thing, I’ve been working with the cursor for several months now and it’s a painful problem

6

I have been providing feedback for a long time
This method has been proposed, but the official has not been able to solve it, and we have no choice
It’s impossible to do unmanned operation at all

1 Like
7

This is extremely annoying - happening also under macOS…
It’s been months…