Cursor fails to run review

Support Bug Reports
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Agent fails to run review on any chat window context. It was working previously, but now is not working at all. I had the infamous ‘no terminal output’ bug, but managed to find a workaround - but I cannot find a workaround for this.
I even tried downgrading the software - still doesn’t work.

Steps to Reproduce

Click ‘Review’
Click ‘Find Issues’

Expected Behavior

Review is meant to work.

Screenshots / Screen Recordings

Screenshot 2025-12-09 104737.png
Screenshot 2025-12-09 104737.png379×121 2.15 KB

Operating System

Windows 10/11

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.1.42 (system setup)
VSCode Version: 1.105.1
Commit: 2e353c5f5b30150ff7b874dee5a87660693d9de0
Date: 2025-12-01T02:18:26.377Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Windows_NT x64 10.0.26200

For AI issues: which model did you use?

I don’t believe the Agent Review model can be changed?

For AI issues: add Request ID with privacy disabled

Failed to run review (request ID: 197886b5-48a1-4b4b-bd9b-6bc508fa1ac1)

Does this stop you from using Cursor

Sometimes - I can sometimes use Cursor

2

Hey, thanks for the report. The error points to a network connection issue. Try these steps:

  1. Disable HTTP/2 (the most common fix):

    • Open Settings with Ctrl+,
    • Search for “HTTP/2”
    • Enable the “Disable HTTP/2” option
    • Restart Cursor

  2. Run network diagnostics:

    • Cursor Settings → Network → Run Diagnostics

  3. Check your firewall and antivirus:

    • Windows may block Cursor (especially after updates)
    • Temporarily turn off the firewall/antivirus to test

  4. If you use a VPN or MCP servers:

    • Try without a VPN
    • Disable unused MCP servers (limit is 80 tools)

If the issue persists, please share the network diagnostics results and mention whether you use a VPN or a corporate network.

3

Hi!

Thanks for the response! It’s fixed now!
It was a billing issue - although it wasn’t flagging it.
Solved.

Cam

4

This topic was automatically closed 22 days after the last reply. New replies are no longer allowed.