When the chat executes terminal in the latest versions not detect the finish of terminal (zsh integrated on vscode/cursor) i’m force to click on “skip” at the end and right side of on terminal chat, and sometimes the ai agent terminates the execution because detects that we cancelled the terminal command.
example after skip a terminated command on chat says "I see the terminal got cut off, but it looks like it started the deployment process … "
In other versions this not happen.
This will cause more spent prompts from premium and paid account!!!
I’m encountering this on both my Linux and Mac machine, but not on my Windows machine for some reason. On my Linux machine I began noticing it in version 0.51.1, and it is still occurring on version 1.0.1.
Multiple other users are reporting this on Github as well:
I’ve discovered that the issue does not seem to be with Cursor itself. At least for me on both of my machines, the issue is related to oh-my-zsh’s Instant Prompt feature.
oh-my-zsh enables this feature by default. I disabled the feature by going to the top of my .zshrc and commenting out the lines related to instant prompt initialization. After Cursor spawned a new terminal, now it is properly seeing when the commands are completed.
also i saw somewhere that i need to put this also # workaround of issue of cursor.ai to be stuck
PROMPT_EOL_MARK=“”
end
but without success… what i said that don’t work as previous versions was the cursor automatic calls the terminal commands and when gets response automatically continue… now i need to click on skip and sometimes the chat terminates instead of analise the response and continue with the next steps…
It seems I’m back to having problems as well. So it may be just an issue with oh-my-zsh in general unfortunately. It works when I replace my .zshrc with a blank one, but I don’t want to do that because oh-my-zsh is too convenient. My workaround is going to be to make Cursor use bash instead of zsh for its terminal, by adding the following to my User settings.json:
I also encountered this problem.
The reason for my problem is that I used the customizable theme powerlevel10k of zsh, which added configuration instructions for the p10k theme in the .zshrc configuration. As a result, Cursor could not correctly judge whether the command was completed when automatically executing the terminal command, causing it to be stuck there.
So in the end I solved the problem by switching to another theme and deleting the configuration directive of p10k in the .zshrc file.
