Hey, thanks for the report. I see three related issues: browser debugging is misleading, the terminal hangs, and the agent breaks already fixed code.
This is a known set of issues. Please check in order:
-
Terminal hangs - most common root cause of the others:
Settings > Agents > “Legacy Terminal Tool” - try toggling it, thenCmd+Shift+P> “Terminal: Kill All Terminals”, restart Cursor.
If you use Oh My Zsh/Powerlevel10k/Starship - they can break the agent’s command completion detection. Details: 🛠️ Guide: Fix Cursor Agent Terminal Hangs Caused by .zshrc -
Browser debugging for backend:
The built-in agent browser is fine for UI tests, but not great for complex backend tasks. For full debugging, use MCP Browser Tools:- Install GitHub - AgentDeskAI/browser-tools-mcp: Monitor browser logs directly from Cursor and other MCP compatible IDEs.
- Chrome extension +
npx @agentdeskai/browser-tools-server@latest - Configure MCP in Settings > Tools & MCP
This gives the agent access to console, network logs, and errors without manual copy-paste.
-
Agent breaks fixed code:
- Use Checkpoints in Composer to roll back: Checkpoints | Cursor Docs
- Start a new chat after 8-10 iterations - old context gets confusing
- Use Review before applying changes: Review | Cursor Docs
-
Extensions can cause hangs:
Runcursor --disable-extensionsand see if it still reproduces.
To diagnose precisely, please share:
- Request IDs of problematic requests (Privacy Mode off): Getting a Request ID | Cursor Docs
- Which shell you use (zsh/bash/fish) and any prompt themes (oh-my-zsh, powerlevel10k, starship)
- A screenshot of the agent’s stuck terminal
- The specific command that hangs
- Your installed Cursor extensions
- Settings > Network > Run Diagnostics - the result
Share the details and I can help more precisely or escalate to the team.