Where does the bug appear (feature/product)?
Cursor IDE
Describe the Bug
For the past few days, Cursor has not been executing terminal commands that I try to run from the agent. I’ve done a clean install, including dumping my caches, and nothing seems to work. It asks to run the command, I give it permission, and then it hangs.
Steps to Reproduce
Ask the agent to run a command (e.g., “run my local dev server”)
Give it permission to run the command
Cursor agent window says it’s running the command, but there’s no output. It just hangs.
Expected Behavior
I would expect the agent window to open a terminal in the background, run the command, show its output, and then clear the prompt window for me to write the next prompt in the agent window.
Screenshots / Screen Recordings
Operating System
MacOS
Current Cursor Version (Menu → About Cursor → Copy)
Version: 1.6.42
VSCode Version: 1.99.3
Commit: 5911e9593196a000b1c00553aaf03b0b32042b90
Date: 2025-09-20T17:16:56.346Z (2 days ago)
Does this stop you from using Cursor
Sometimes - I can sometimes use Cursor
14 Likes
THis is happening to me too!!! I edited my .zshrc file as suggested by some and it STILL DOES NOT WORK. CURSOR QA ■■■■■.
1 Like
The same thing is happening to me.
1 Like
deanrie
(Dean Rie)
September 23, 2025, 3:52am
4
Hey, thanks for the report. We’re aware of this issue and the team is working on a fix.
2 Likes
yellowful
(yellowful)
September 23, 2025, 6:56am
6
Simularlly, just in my situation, there is no run and skip buttons appeared at the bottom right corner.
B353N
(Rumen Slavov)
September 23, 2025, 8:11am
7
in my opinion with lasts updates they broke up agent terminal …. so yea same situation here
2 Likes
Same issue here…
Version: 1.6.45
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: Linux x64 6.14.0-29-generic
1 Like
petun
(petun)
September 23, 2025, 1:32pm
9
The same:
Version: 1.6.45
VSCode Version: 1.99.3
Commit: 3ccce8f55d8cca49f6d28b491a844c699b8719a0
Electron: 2025-09-22T18:22:38.013Z
ElectronBuildId: 34.5.8
Chromium: undefined
Node.js: 132.0.6834.210
V8: 20.19.1
ОС: 13.2.152.41-electron.0
If I ask the agent to run some command, it takes too much time. For example:
cd /project && git diff master…new-branch --name-only
This command run takes about a minute in Agent terminal, but in separate zsh terminal it takes less than a second.
1 Like
rfelix
(Ricardo)
September 23, 2025, 2:44pm
10
Same issue
Version: 1.6.45
VSCode Version: 1.99.3
Commit: 3ccce8f55d8cca49f6d28b491a844c699b8719a0
Date: 2025-09-22T18:22:38.013Z (20 hrs 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.1.0
1 Like
xcono
September 23, 2025, 2:53pm
11
I can confirm it times out after about a minute (Ubuntu 22.04, zsh).
Switching to bash has no effect.
Downgrading to 1.5 works.
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: Linux x64 6.8.0-79-generic
1 Like
samirspatel
(Samir Patel)
September 23, 2025, 5:13pm
12
I thought the terminal was already fixed a couple versions ago, this is a regression
tony-wang
(Tony)
September 23, 2025, 5:23pm
13
Yup, ran into the exact same issue and someone on the dev team recommended me to downgrade to 1.5.11. Immediately fixed the issue.
1 Like
rfelix
(Ricardo)
September 23, 2025, 6:08pm
14
how can you downgrade to a diff version?
mwjt42
September 23, 2025, 6:16pm
15
Links to historic versions here:
Direct download links for the latest release of the Cursor AI-enabled IDE code editor
Uninstall Cursor, and reinstall your preferred version.
2 Likes
cmkl26
(ML)
September 23, 2025, 8:15pm
16
Same issues with agent not running any command in Ubuntu through WSL (24.04, zsh)
Version: 1.6.45 (system 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
You can downgrade to v 1.5.11 (as mentioned in the thread) as a workaround while we’re waiting for a fix to be deployed.
Having the same issue in case it helps:
Version: 1.6.45 (Universal)
VSCode Version: 1.99.3
Commit: 3ccce8f55d8cca49f6d28b491a844c699b8719a0
Date: 2025-09-22T18:22:38.013Z (1 day 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.6.0
Version: 1.6.45
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: Darwin arm64 24.6.0
Downgraded to 1.5 and it worked, but it auto updated again etc and stopped.