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

**URL:** <https://forum.cursor.com/t/terminal-getting-stuck-hangs-stalls-forever-not-displaying-output-in-windows-auto-run-agentic-mode/117747>\
**Category:** Bug Reports\
**Created:** [July 14, 2025, 4:39pm UTC](https://forum.cursor.com/t/terminal-getting-stuck-hangs-stalls-forever-not-displaying-output-in-windows-auto-run-agentic-mode/117747 "2025-07-14T16:39:03Z")\
**Posts on this page:** 1\
**Showing post:** 8

<div class="post-metadata">

**Author:** ![Oliver\_Michalik](https://avatars.discourse-cdn.com/v4/letter/o/ce7236/32.png) [@Oliver\_Michalik](https://forum.cursor.com/u/Oliver_Michalik)\
**Post date:** [July 14, 2025, 7:11pm UTC](https://forum.cursor.com/t/terminal-getting-stuck-hangs-stalls-forever-not-displaying-output-in-windows-auto-run-agentic-mode/117747/8 "2025-07-14T19:11:58Z")

</div>

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 remains.

When the agent tries to reuse previous terminal, sometimes I see no terminal output.

---

_[View the full topic](https://forum.cursor.com/t/terminal-getting-stuck-hangs-stalls-forever-not-displaying-output-in-windows-auto-run-agentic-mode/117747)._