Hey, thanks for the report. This pattern (works at first, then fails when reading terminal output) matches a known Agent bug when handling certain terminal exit codes or large output.
Quick fixes to try:
Disable HTTP/2 (most common fix):
- Cursor Settings
Ctrl/Cmd+, → search “HTTP/2” → enable “Disable HTTP/2” → restart Cursor
Check MCP servers (if configured):
- Cursor has an 80‑tool limit that can cause connection failures
- Disable any MCP servers you’re not actively using
Windows Firewall:
- Your Windows firewall may need to re‑allow internet access for version 2.0.69
To help the investigation, please capture console logs when the error happens:
- Help → Toggle Developer Tools → Console tab
- Reproduce the error with your Node command
- Screenshot or copy any red errors from the Console
- Share here along with another Request ID from the failed connection
Similar issue with terminal output: The cursor cuts off the execution of the code at the stage
Let me know if disabling HTTP/2 helps.