# Agent Run/Execute shows No output and does not return real stdout in project windows on macOS **URL:** \ **Category:** Bug Reports\ **Tags:** terminal, macos\ **Created:** [March 10, 2026, 9:06pm UTC](https://forum.cursor.com/t/agent-run-execute-shows-no-output-and-does-not-return-real-stdout-in-project-windows-on-macos/154344 "2026-03-10T21:06:27Z")\ **Posts on this page:** 1\ **Showing post:** 6
**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:** [March 11, 2026, 7:10am UTC](https://forum.cursor.com/t/agent-run-execute-shows-no-output-and-does-not-return-real-stdout-in-project-windows-on-macos/154344/6 "2026-03-11T07:10:37Z")
Great, that confirms the issue. Terminal v3 can’t create a session, so every command ends up timing out. The same error showed up in [this thread](https://forum.cursor.com/t/agent-terminal-commands-never-return-output-always-hit-30s-timeout-macos-zsh/153775), and it was fixed in two different ways. Since you don’t have MCP set up, let’s try this step by step: 1. Legacy Terminal Tool This is the fastest way to bypass v3 right now. Open Cursor Settings `CMD+Shift+J` \> Agents \> enable Legacy Terminal Tool. Then run `CMD+Shift+P` \> `Terminal: Kill All Terminals`, fully restart Cursor, and try again. Legacy uses the older mechanism and doesn’t depend on the v3 health check. 2. Clean zsh profile If Legacy doesn’t help, temporarily rename `~/.zshrc` to `~/.zshrc.bak` and restart Cursor. Some plugins (oh-my-zsh, powerlevel10k, etc.) can conflict with terminal capture. In that thread, this is what fixed it for one user. 3. No extensions Run `cursor --disable-extensions` from your normal terminal, open the project, and test again. Let me know which step worked (or didn’t), and we’ll dig in further. --- _[View the full topic](https://forum.cursor.com/t/agent-run-execute-shows-no-output-and-does-not-return-real-stdout-in-project-windows-on-macos/154344)._