"Find Issues" / Agent Review in Source Control consistently fails

Support Bug Reports
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Failed to run review (request ID: e2636a63-ce3f-4979-ab6e-ae1ec89bc3cd)
This happens on every attempt, including after restarting Cursor, updating Cursor, signing out/in, and testing on a mobile hotspot (same failure).

Relevant log evidence (from Cursor Structured Logs / Agent Review output):

  1. Agent Review context succeeds:
    Generated Agent Review context with 60 files and 0 rules, diff size: 178.4189453125kb
  2. Review API returns minimal payload:
    service: aiserver.v1.AiService
    method: StreamBugBotAgentic
    requestId: f42d2e3f-4362-4fc8-85db-5abcaa613260
    chunkSize: 61
    “Stream completed successfully” (but UI shows Failed to run review)
  3. Auth/entitlement warnings on startup:
    service: aiserver.v1.DashboardService
    method: GetTeamCommands
    ERROR_UNAUTHORIZED
    detail: “You must be a team member to access this resource”
    analyticsMetadata.actionRequired: “login”
  4. Intermittent auth readiness warnings:
    “Timeout waiting for auth ready signal”
    “BackendClient proceeding without auth ready (timeout or logged out)”
    Troubleshooting already done:
  • Signed out and signed back in (Pro still shown in UI)
  • Updated Cursor to latest stable
  • Tested on mobile hotspot (still fails)
  • Not using VPN/proxy
  • Regular chat/agent features work; only SCM Agent Review fails

Steps to Reproduce

  1. Make local git changes (currently ~60 changed files, ~178 KB diff)
  2. Open Source Control (Ctrl+Shift+G)
  3. Click “Find Issues” / Agent Review
  4. Error appears immediately: “Failed to run review (request ID: …)”

Operating System

Windows 10/11

Version Information

Version: 3.11.19 (user setup)
VS Code Extension API: 1.125.0
Commit: bf249e6efb5b097f23d7e21d7283429f0760b740
Date: 2026-07-12T21:39:24.175Z
Layout: IDE
Build Type: Stable
Release Track: Default
Electron: 40.10.3
Chromium: 144.0.7559.236
Node.js: 24.15.0
V8: 14.4.258.32-electron.0
xterm.js: 6.1.0-beta.256
OS: Windows_NT x64 10.0.26200

Does this stop you from using Cursor

No - Cursor works, but with this issue

5

Hey, thanks for the detailed report. The logs and Request ID help a lot.

From the data, it looks like the review context builds fine and the request gets sent, but it fails during execution. To figure out where it breaks, I need a couple things:

  1. Open the output channel Cursor Agent Review in View > Output, then pick “Cursor Agent Review” in the dropdown, and check the logs right when it fails. I’m looking for a line like Error computing local context: RangeError: Maximum call stack size exceeded or any other explicit error near the failure. Please paste that part of the logs.

  2. Try running “Find Issues” on a smaller subset of changes, like staging just a few files instead of all 60 (~178KB). I want to see if the review works on a small diff.

This should help narrow down whether it’s hitting a diff size limit or something else. Let me know what the logs show.

6

Thank you very much for the answer - I have run “Find Issues” on smaller subset of changes and it worked properly, so I assume the size was the probem (I got a bit confused when I discussed the issue with cursor agent as it was suggesting the problem was in access due to aut…)

Anyway, in that case, all looks good, will run it more often on smaller set of changes :slight_smile:

Thanks and have a nice day!
Jan

8

@Jan_Poliak glad we figured it out. Yeah, it’s the diff size. On a big change set like yours, about 60 files and about 178 KB, Agent Review currently crashes. That’s a limit on our side, not an access issue. The auth warnings in the logs like You must be a team member are normal noise for a Pro account without a team and they’re not related to the review, so the agent was a bit misleading there.

Running it on a smaller subset of changes is the right workaround for now. I’ve reported the crash on large diffs internally so we can fix the limit. I can’t share an ETA yet, but I’ll post an update in the thread when I have one.

Have a great day.