Hey, thanks for the detailed report. This is a known issue. We’ve seen it in several reports, especially on macOS with zsh.
A few things to check:
-
Stale working directory
This is the most common cause. Even if the folder exists now, if it was ever moved or renamed, the workspace state might still point to an old path. Try closing Cursor completely, then reopen the project viaFile > Open Folderfrom the real current path. -
Start a fresh chat
In several cases, the issue was session-specific. The terminal broke mid-session, but a new Agent chat worked fine. Worth trying first. -
Kill all terminals first
RunCMD+Shift+PthenTerminal: Kill All Terminals, then restart Cursor fully. -
Check DevTools
Go toHelp > Toggle Developer Tools > Console, then run a command via the agent. Look forENOENTerrors or anything path-related. That would confirm the stale directory idea.
If none of that helps, I’ll need:
- The Request ID from the failing chat (top right of chat > Copy Request ID)
- A screenshot of the DevTools Console output after running a command
Some related threads for reference:
- Terminal Command Output Capture Completely Broken
- Agent terminal: no stdout in tool result (solved, stale path)
The team is aware of this pattern. Let me know what DevTools shows.