Hi all,
I’ve been trying to use Cursor to automate the installation process of our application which requires multiple commands to be run in a variety of directories. The only issue I am facing right now is when a command takes a long time to run, Cursor typically exits (CTRL+C) the terminal before the process has finished.
Right now I pop out the terminal and tell composer to wait until I confirm the process is finished. Is there any way I can prevent the early CTRL+C?
Thanks for reporting. I have seen a couple reports of the Composer killing its own tasks, but I will feed back to the team to see if we can get this sorted!
It happened to me here too, this is really stupid.
I’m on version 0.47.1
Happens consistantly when running git push command.
Happens for me when running lando commands in wsl2. The command is instantly killed with ctrl C, cursor doesn’t realise that has happened and won’t stop doing it no matter if its told not to.
i have the opposite issue now. the command will finish, but the agent isnt getting the message. all i can do is hit move to background, and then quickly hit stop before the agent complains ive moved it to background. then copy paste the output back into chat.