Just hanging on this
Having the same issue on Ubuntu 24.04, WSL2, zsh as the environment shell.
Thanks for this. We are investigating
Same issue on my side. For now I downgraded to v1.5
the same here on mac. noticed it not working nearly week ago, i thought i’ll reinstall stable version later to fix it as i was on the early access one before, but then reinstalled today and still not working. ofc removed all cursor data dirs before it.
I’m seeing the same issue on Windows with a powershell terminal. In previous versions, I could still copy the output from the terminal to get the agent to keep working, but I can’t do that anymore.
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.5.0
same issue
I’m also blocked on this, ran some analysis and it’s saying it’s Webkit TCC blocking?
The Primary Blockers
1. TCC (Transparency, Consent, and Control) Framework
The most significant blocker is macOS’s TCC framework. The logs show numerous XPC_ERROR_CONNECTION_INVALID errors when WebKit processes (which Cursor uses for its UI and integrated terminal) attempt to make TCCAccessRequest() calls. This indicates that Cursor is being denied access to various system resources at the TCC level.
2. macOS Sandbox Restrictions
The logs are filled with “Sandbox restriction” errors (error 159) from launchd affecting various system services and applications, including com.apple.WebKit (related to web content processes within Cursor). This indicates that macOS’s own sandbox mechanisms are heavily restricting processes.
Cursor’s terminal commands are being blocked by macOS’s built-in security mechanisms (TCC and sandbox)
Potential Solutions
-
TCC Permissions: Cursor may need explicit TCC permissions for terminal access
-
Sandbox Entitlements: Cursor might need additional sandbox entitlements to execute terminal commands
-
Application Signing: The application may need to be properly signed with the necessary entitlements
As a windows user I don’t seem to have the same bug however when it’s done running a command it don’t see the command is done so it will wait until tool time out. If you press enter it often say the command failed to run and it will try all the commands it can unless you say “the command ran fine or the command failed”
FWIW, this is the same issue I have. It started after 1.6.27, and has persisted all teh way up through 1.7.11 as of my own testing. You can revert to 1.6.27 and that will get the terminals working again. They occasionally still hang and you have to fiddle to get things working again, but for the most part 1.6.27 works and terminal usage by the agent works, whereas anything after that, and terminals DO NOT seem to function.
As far as I can tell, a terminal instance is not even being created, so you can’t even open it and check on it. The agent seems to hang here before it even creates a terminal instanc.
See my issue for more details:
This has always happened with me in Windows. I just tell it not to try running commands and run them myself.
Happened to me as well, sometimes it will run the command but there is no output at all, sometimes it’s just gets interrupted on its own and the the Agent says that it was interrupted by the user. I’m using Windows, and only happened if it is an instance of Cursor Terminal, and it will always have Terminate batch job (Y/N)? as if I was Interrupting the command. Using ctrl+ command on it wont result the expected command and instead print out this:
^V^V^V^V^V^V^S^S^S^S^S^S^S^W^W^W^W^W^W^Q^Q^Q^Q^E^E^E^R^R^R
It doesn’t happen when I spawn the terminal
This one, I don’t even cancel the command, but still it says I am cancelling it
The issue has been around for a while, but since the last update, it happens consistently
Same issue, exactly as described by OP.
Version: 1.7.12
VSCode Version: 1.99.3
Commit: b3f1951240d5016648330fab51192dc03e8d7050
Date: 2025-09-28T00:58:08.696Z
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
It’s been a week and this is hurting me. Would appreciate it if there was an update or workaround. I’ve tried some of the ideas online for modifying my .zshrc but it hasn’t fixed it.
Version: 1.7.22 (Universal)
VSCode Version: 1.99.3
Commit: 31b1fbfcec1bf758f7140645f005fc78b5df3550
Date: 2025-09-29T21:47:28.451Z (6 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.6.0
I can confirm, that on 1.7.17 the terminal commands now work.
Version: 1.7.17
VSCode Version: 1.99.3
Commit: 34881053400013f38e2354f1479c88c9067039a0
Date: 2025-09-29T03:10:26.099Z
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
P.S. @bencancode - for me 1.7.17 is the latest version (“Check for updates” says “There are currently no updates available.”), I’m curious about 1.7.22. Maybe the difference comes from the fact, that I’m installing the ARM64 version and you are using Universal.
I am in 1.7.23 and still not fixed
Version: 1.7.23
VSCode Version: 1.99.3
Commit: 5069385c5a69db511722405ab5aeadc01579afd0
Date: 2025-09-30T02:52:09.100Z
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-32-generic
Interesting point about it working on ARM64, I’m on M2 Macbook. Just upgraded to 1.7.23 and like Shashank_Salian it’s still not working.
Is 1.7.23 on ARM64 or Universal? For me 1.7.17 is the latest possible version for ARM64.