# Agent Shell Tool Fails on Windows - pid: -1, no command output

**URL:** <https://forum.cursor.com/t/agent-shell-tool-fails-on-windows-pid-1-no-command-output/145331>\
**Category:** Bug Reports\
**Created:** [December 5, 2025, 7:38am UTC](https://forum.cursor.com/t/agent-shell-tool-fails-on-windows-pid-1-no-command-output/145331 "2025-12-05T07:38:33Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![deanrie](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/deanrie/32/1263_2.png) [@deanrie](https://forum.cursor.com/u/deanrie)\
**Post date:** [December 5, 2025, 10:21am UTC](https://forum.cursor.com/t/agent-shell-tool-fails-on-windows-pid-1-no-command-output/145331/3 "2025-12-05T10:21:39Z")

</div>

Hey, thanks for the detailed report and for the Git Bash workaround - super helpful.

This is a known regression in the new Windows terminal. We’re tracking it here: [Cursor version 2.1.39 has terminal bug](https://forum.cursor.com/t/cursor-version-2-1-39-has-terminal-bug/144368)

To help us fix it faster, please attach:

- Logs from Help → Toggle Developer Tools when the agent tries to run a command
- Output from “Extension Host” and “Shared Process” at the time of the error
- The result of launching Cursor with `--disable-extensions`

I’ll link your case to the existing issue.

---

_[View the full topic](https://forum.cursor.com/t/agent-shell-tool-fails-on-windows-pid-1-no-command-output/145331)._