Sometimes the terminal wont reach a natural termination point and stay alive, but will have encountered an issue. I have to manually cancel it, then it proceeds to understand what went wrong and fix it. Which is amazing. But if the agent could periodically view the output and realize when it’s stuc…

Isnt a timeout already integrated? perhaps this should be a bug report. But overall i agree, sometimes the timeout isn’t fast enough as it waits for more.

Yeah in my case, I never see any timeout. If there is one, it’s not mentioned in the settings. Not clear that this is a bug.

I used recently console output and it stopped watching by itself. However i have also noticed that it sometimes didnt stop. So i think this needs at least clarified how it is processed and how it decides when to stop.

It happened to me here too. I’m on version 0.47.1

Related: [image] Terminal getting stuck, hangs, stalls forever, not displaying output in windows (auto-run agentic mode) Bug Reports Describe the Bug There are a lot of related posts/bugs about terminal not working properly, but none properly describes what is …

Example of terminal being stuck. Jest does not exit when this error happens. Agent keeps waiting forever, I must manually input Ctrl+C to end it [Screenshot_659]

It also happens to me and to some coworkers. Is this being taken care of? In my case, it takes a very long time to solve/close the terminal, and most of the time, it gets stuck, forcing me to restart the console, close it manually, or pray to the gods to work…

@Jose_Gomez Could you post a full separate Bug Report with more info Create Bug Report Also add a Request ID with privacy disabled so we can look into the details? Cursor – Getting a Request ID We have solved several of such issues on 1.4.x and 1.5.x but if you still have them then kindly fill in …

I think I know why this issues occur. when I open the Cursor it all working well and suddenly it start to lose the task ended signal, so I notice it occur each time the OMZ make an update while the cursor is open and from that point it stop identify the command ended. restart the cursor solved it …

Have the agent intelligently watch console output to terminate when stuck

Ideas Feature Requests

Oliver_Michalik (Oliver Michalík) July 14, 2025, 5:03pm 6

Topic		Replies	Views
Terminal getting stuck, hangs, stalls forever, not displaying output in windows (auto-run agentic mode) Bug Reports	8	1599	July 14, 2025
Terminal commands get stuck on running Bug Reports	3	461	July 15, 2025
Agent hangs on terminal commands that complete successfully? Bug Reports	0	696	March 24, 2025
Agent gets stuck after successfully executing terminal commands Bug Reports	4	694	August 1, 2025
Terminal sometimes doesn't wait for command to finish Bug Reports	4	242	July 28, 2025

Have the agent intelligently watch console output to terminate when stuck

Related topics