Where does the bug appear (feature/product)?
Cursor IDE
Describe the Bug
Version: 1.6.14 (user setup)
VSCode Version: 1.99.3
Commit: 64b72c9cd7e38203078327f881d5fe74930b2600
Date: 2025-09-11T21:41:40.820Z
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
it happens for every command ever since i updated to new version.
image.png
it is adding $ before every command due to which command does not run.
fd1387f0-6759-4bad-b386-ff6baad1462f
Steps to Reproduce
when connected to server via SSH and agent any command it adds $ in front of it because of that no output is received.
Screenshots / Screen Recordings
Operating System
Windows 10/11
Current Cursor Version (Menu → About Cursor → Copy)
Version: 1.6.14 (user setup)
VSCode Version: 1.99.3
Commit: 64b72c9cd7e38203078327f881d5fe74930b2600
Date: 2025-09-11T21:41:40.820Z
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?
sonnet 4
Does this stop you from using Cursor
Yes - Cursor is unusable
andrewh
September 12, 2025, 4:19pm
3
Could you try restarting Cursor and reporting back to us?
For me too, the terminal keeps getting stuck and does nothing. It freezes.
req id : 2607b69e-00a1-4ee3-ab07-05c98985f05a
andrewh
September 12, 2025, 4:34pm
5
Could you post your “Menu → about cursor → copy” platform and version info?
SĂĽrĂĽm: 1.6.14 (user setup)
İşleme: 1.99.3
Tarih: 64b72c9cd7e38203078327f881d5fe74930b2600
Electron: 2025-09-11T21:41:40.820Z
ElectronBuildId: 34.5.8
Chromium: undefined
Node.js: 132.0.6834.210
V8: 20.19.1
İşletim Sistemi: 13.2.152.41-electron.0
mode : AUTO
fouli
September 12, 2025, 5:13pm
7
Hi,
Having exactly the same problem after updating also
Version: 1.6.14 (user setup)
VSCode Version: 1.99.3
Commit: 64b72c9cd7e38203078327f881d5fe74930b2600
Date: 2025-09-11T21:41:40.820Z
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
Hope having a solution soon !
I can’t work because of this problem, please fix the problem.
andrewh
September 12, 2025, 5:51pm
9
We’re fixing this right now - apologies.
6 Likes
Seems to be fixed for me. Thank-you
when will this problem solve?
still broken for me, same message after closing and restarting, and reinstalling
Version: 1.5.11 (Universal)
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: Darwin arm64 24.6.0
Failed to read file.
(Request ID: c46bb720-89e4-418c-a2b1-768717e14e3a)
Terminal isn’t work for me as well, any command just hangs there forever. Running on WSL2. No amount of restarts change the behavior.
I then restarted wsl (wsl –shutdown
) and then the terminal didn’t hang, but it also immediatelly returns without actually running the command, it just “pretends” it did.
Version: 1.6.14 (user setup)
VSCode Version: 1.99.3
Commit: 64b72c9cd7e38203078327f881d5fe74930b2600
Date: 2025-09-11T21:41:40.820Z
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
condor
September 14, 2025, 3:37pm
15
@Richard_Albright the fix will be in 1.6.x
When will the terminal bug be fix, it’s been more then 3 days!!!
Version: 1.5.11
VSCode Version: 1.99.3
Commit: 2f2737de9aa376933d975ae30290447c910fdf40
Date: 2025-09-05T03:48:32.332Z (1 wk 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 22.5.0
Version: 1.6.23 (Universal)
VSCode Version: 1.99.3
Commit: 9b5f3f4f2368631e3455d37672ca61b6dce85430
Date: 2025-09-15T21:49:07.231Z
Electron: 34.5.8
Chromium: 132.0.6834.210
Node.js: 20.19.1
V8: 13.2.152.41-electron.0
OS: Darwin arm64 23.6.0
the default location is / , we expected the default location is the current workspace. cannot run any command as before
1 Like
Kazopl
September 16, 2025, 1:13pm
18
Same issue for Remote SSH also
B353N
September 17, 2025, 7:10am
20
Hey , when cursor try to run any docker command this is happening in cursor terminal
$ ms artisan test --filter=“MaxDiscountCheckoutFixTest”
the input device is not a TTY
$ ms artisan test --filter=“MaxDiscount” --stop-on-failure
the input device is not a TTY
This error is happening after last upgrade the input device is not a TTY
Version: 1.6.26
VSCode Version: 1.99.3
Commit: 6af2d906e8ca91654dd7c4224a73ef17900ad730
Date: 2025-09-16T17:12:31.697Z
Electron: 34.5.8
Chromium: 132.0.6834.210
Node.js: 20.19.1
V8: 13.2.152.41-electron.0
OS: Darwin arm64 25.0.0
jrista
September 19, 2025, 10:40pm
23
It seems like very rudimentary commands even can cause terminals to hang or get stuck. Been sitting at this one for almost 5 minutes (was chatting with a coworker)…its just stuck:
This also seems to be becoming a more and more frequent issue. When I first switched to 1.6, I maybe encountered it once a day. Its many times a day, closing in on once an hour almost, now… (Don’t even know how to account for that.)
MODEL (for above): claude-4-sonnet
Version: 1.6.26
VSCode Version: 1.99.3
Commit: 6af2d906e8ca91654dd7c4224a73ef17900ad730
Date: 2025-09-16T17:12:31.697Z
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
deanrie
September 20, 2025, 9:29am
24
Hey, thanks for the report. Could you please update to v1.6.35 and let me know if the issue persists?
It still persists for me, been stuck here for 10 minutes.
Version: 1.6.35 (user setup)
VSCode Version: 1.99.3
Commit: b753cece5c67c47cb5637199a5a5de2b7100c180
Date: 2025-09-19T17:39:38.846Z
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
1 Like