Describe the Bug There are a lot of related posts/bugs about terminal not working properly, but none properly describes what is happening or offer solutions. The problem: When Agentic mode is running terminal commands, sometimes it does not show output and stalls forever, preventing the agent conti…

Upon further inspection, I can confirm that the agent it trying to reuse previos terminal sessions. The no output box bug happens when the terminal is reused. First command always work correctly. It also looks like the hanging is not caused by this bug itself, but rather a related bug that agent ca…

I have partially fixed this problem with additional instructions for the AI Rule: For every command, the agent must always start a new terminal session (e.g., using a fresh shell invocation). Rule: If the command was canceled, always re-run the canceled command in a new terminal session with a fr…

Related: [image] [BUG] Terminal tool gets stuck after exit code Bug Reports This is still a problem. Related fully described problem, with additional bugs:

Related: [image] Have the agent intelligently watch console output to terminate when stuck Feature Requests 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 u…

Hey, thanks for the report. I’ve already logged this issue in our internal tracker so the team can look into it.

Thanks @deanrie , I belive this is the same issue we’re seeing (sadly again) with Zsh and ‘q’: [image] Without doubt, the MOST frustrating Cursor issue is STILL: zsh: command not found: q Bug Reports @danperks Any update on this? Some users are reporting it was resolved, s…

I have been seeing this too on windows PowerShell and Command Prompt terminals. After I switched to git bash, I have never since seen the “command not found: q” issue. However, this seems to be a different terminal bug, because even on git bash, the issue with missing terminal output box still rema…

A hacky but somewhat reliable solution is the additional instruction (Rule) to always start a new terminal session I mentioned previously. Clicking the “Move to background” works more often than clicking skip, because when you click skip it almost always ends the agent by asking “User cancelled the …

Terminal getting stuck, hangs, stalls forever, not displaying output in windows (auto-run agentic mode)

Support Bug Reports

Oliver_Michalik (Oliver Michalík) July 14, 2025, 5:02pm 4

Topic		Replies	Views
Terminal commands get stuck on running Bug Reports	3	478	July 15, 2025
Cursor agent hangs executing terminal commands after about 5 commands Bug Reports	1	225	July 15, 2025
Agent not exiting out of terminal execution and gets stuck Bug Reports	3	1261	June 25, 2025
[Bug] Cursor Agent terminal doesnt show/read output in chat Bug Reports	3	438	December 23, 2025
Agent keeps getting stuck and can only continue after "Move to background" Bug Reports	21	3258	July 21, 2025

Terminal getting stuck, hangs, stalls forever, not displaying output in windows (auto-run agentic mode)

Related topics