Hey, this is a known issue. We’ve seen several reports of this on macOS, especially with zsh.
You’ve already done a lot of troubleshooting, so let’s focus on the things you haven’t tried yet:
-
DevTools console: This is the most important step right now. Go to
Help > Toggle Developer Tools > Console, then ask the agent to runecho test. Look for errors likeENOENT,createSession timeout, or anything path-related. A screenshot of the console output would help a lot. -
Legacy Terminal Tool: Go to Cursor Settings
CMD+Shift+J> Agents > enable Legacy Terminal Tool. Then runCMD+Shift+P>Terminal: Kill All Terminals, fully restart Cursor, and try again. -
Disable extensions: Run
cursor --disable-extensionsfrom a normal terminal, open the project, and check if the agent can capture output. This helps rule out extension conflicts. -
Clean zsh profile: Temporarily rename
~/.zshrcto~/.zshrc.bakand restart Cursor. Some zsh plugins (oh-my-zsh, powerlevel10k, etc.) can break terminal capture. In one similar report, removing~/.zshrcfixed the issue completely. -
Re-open via File > Open Folder: Since the problem is project-specific (an empty window works fine), there might be a stale working directory reference. Close Cursor, reopen it, and use
File > Open Folderto open the project from scratch.
The fact that it works in an empty window but not in project windows is an important clue. The DevTools output will tell us exactly what’s going wrong.
Related threads:
- Agent terminal commands never return output (macOS, zsh) - solved, MCP servers or
.zshrcwere the cause - Agent terminal: no stdout in tool result - solved, stale working path
Let me know what DevTools shows and we’ll go from there.