Agent Review no longer works at all

Support Bug Reports
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Previously, Agent Review would not work automatically on my workspace (which has git repos in subdirectories), but if you called it on some changes from the Review screen using the Find Issues button it would work (and actually was really useful, unlike everything else on the Review screen).

However as of I think the previous release (it was happening on Friday and Cursor auto-updated this morning, and it’s still happening), this no longer works - it just immediately shows “Agent Review found no changes to review”. I’ve tried various combinations of accepting changes, selecting All vs Pending changes in the review screen etc, but no luck - always the same message.

Steps to Reproduce

Make sure your Cursor workspace does NOT have a git repo in the root, but DOES in a subdirectory.
Use an agent to make some changes in that subdirectory.
Press Review then Find Issues (or any OTHER method of triggering agent review as far as I can see, but Review->Find Changes worked previously on this repo)

Expected Behavior

The agent review should pick up on the changes as it did previously, and run as normal.

Operating System

MacOS

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.3.34
VSCode Version: 1.105.1
Commit: 643ba67cd252e2888e296dd0cf34a0c5d7625b90
Date: 2026-01-10T21:17:10.428Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Darwin arm64 25.2.0

Additional Information

This is a pity, as I found agent review to be REALLY useful at times, it was the only real feature from the 2.x branch that I actually found to be a major improvement.

Does this stop you from using Cursor

No - Cursor works, but with this issue

3

Hey, thanks for the report. This is a known issue. The same bug showed up for several users after updating to 2.3.34: Agent instantly reports "no changes to review" with Find Issues

The team is working on a fix. It happens most often when the workspace root isn’t a git repo and the git repos are in subdirectories, which matches your setup.

Temporary workaround: try opening the specific subdirectory that contains the git repo directly in Cursor instead of the top-level workspace. In those cases, Agent Review usually works.

I’m tracking this issue for the team.