I have a web app that I am building in which I use Docker containers for the server, client, etc. For production, we use fly.io to deploy—and I off within SSH into these machines to control them.
I love using the ability to have Cursor help write CLI commands. I find that Cursor continuously gets hung up perpetually once making a command, though. It might be a simple command such as “ls” and it essentially is unable to end the command within the Cursor chat window or see that the proper result has been returned and move on.
Does anyone face a similar problem? Any suggestions? Having Cursor be able to detect that the full result was given in the CLI and move on would help increase the speed of work significantly.
Hi Daniel, I had the same issue with all Terminal commands. Resolved by:
(1) Closing my open Terminal window
(2) It hung an hour later. After opening and closing the IDE terminal window, I am now able to watch the terminal commands run.
(3) Now everything is hanging again. Closing and opening did not work.
Hey everyone, a couple days on from this initial post, I think I have a little bit more feedback. Things appear to run better when the terminal windows are closed—which I don’t love, because I do want to watch terminal commands execute and logs actively roll into the terminal.
When the terminal window is closed in cursor the issue is lessened. Still, certain types of commands get hung up, such as when I SSH into my production server and write commands to show server logs in terminal. Cursor seems to not understand when the command has successfully run (we get back logs to study). Thank you.
I can see how this might be an issue: there’s not a concrete understanding by Cursor about what the intent of the command was, what successful return of that command is, and therefore it’s not moving on to the next command.
