for me with zsh and p10k it was working until it didn’t any more…using wsl for testing (writing a zsh plugin)
ok nevermind, fixed it by actually learning how to use the software properly…
Who’ve got access to 0.47, is it fixed there?
I noticed it sometimes gets stuck even in 0.45 but it does not happen very often. In 0.46 it simply never woks. Crossing my fingers they fixed it in 0.47
Nope, it is not fixed in 0.47, rolling back to 0.45 again
Getting the same issue!
Anyone has figured out the workaround?
I’m experiencing the same issue. And it’s significantly reducing my productivity.
@deanrie could you please confirm that this is a known issue and cursor team is working to fix it? So far I’ve got zero feedback and it looks like the issue is completely ignored.
1 Like
I’m experiencing the same issue. Is there further verification it is only an issue with zsh and p10k?
I’m using fish and I tried default bash a well, for me it happens everywhere, regardless of the shell.
Same problem, very annoying when testing and fixing bugs…
@danperks can we get the fix please?
This bug is making Cursor ALMOST unusable. It’s impossible to quickly check my SQLite db with the terminal not working from the chat. Anyone find a work around?
Mine is doing something weird where it will like cache a command, and Cursor will be trying to run a completely different command than the chat wants to run.
1 Like
Yep, I usually let cursor write tests and run them but since 0.45 it does not work anymore
Hey, sorry about this, do you have a minimal reproduction I can test?
Hm I’m not sure how to do that, it does not work for me with any shell, and it looks like I’m not the only one.
It works in 0.45
Version: 0.45.17
VSCode Version: 1.96.2
Commit: 7c00f62dd81412c8defe2b64b4d32d06e0a7e720
Date: 2025-02-26T19:15:49.861Z
Electron: 32.2.6
Chromium: 128.0.6613.186
Node.js: 20.18.1
V8: 12.8.374.38-electron.0
OS: Darwin arm64 24.3.0
But it does not only any older version.
I can see in the terminal output that the command had finished execution, but the ui still shows it as loading and it is not finishing until I manually cancel or popup the terminal
It appears the issue happens when Shell Integration in VSCode is disabled. I had to disable it because it conflicts with the Fish shell.
2 Likes
Hi, sorry, but the issues are not resolved on my setting with this option. It actually doesn’t matter if the shell integration is enabled or disabled. I can see in the terminal output that the command has finished execution, but the UI still shows it as loading, and it is not finishing until I manually cancel or popup the terminal.
Here is my configuration:
Version: 0.47.5
VSCode Version: 1.96.2
Commit: 53d6da1322f934a1058e7569ee0847b24879d180
Date: 2025-03-14T21:41:01.221Z
Electron: 32.2.6
Chromium: 128.0.6613.186
Node.js: 20.18.1
V8: 12.8.374.38-electron.0
OS: Darwin arm64 24.3.0
Attached, you see a screenshot of the behavior. It finished but Cursor does not realize this.
1 Like
Same, it keeps trying to use the same command from before, like it is cached or something. Then even when I get it to use the correct command it just spins and never pulls my data from the db…
In my case it just hangs and nothing’s happening (running 0.47.8).
And if I pop it out this is what I see and it just continues with next command assuming that this one was successful even though it didn’t run at all, even in popped out terminal.
In other cases I have to pop out the terminal (the command in it finishes successfully), but it tries to run it again, because it’s obvious that it can’t read output from popped out terminal. Very frustrating.
I’m using Remote SSH though to develop on remote server, but I’m not sure its really related.
While I was writing this, the following command in the same request worked:
1 Like