"Waiting for Review" while building agent plan

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

When trying to build from a plan, the agent started filling a file with contents but then stopped with a “Waiting for Review” text in tiny dark grey text on a dark grey background. The button next to the text says “Review” but only causes a toast in the bottom right corner (completely opposite side of the screen) stating “No changes to review”. There are no other apparent UI elements to make the agent continue with building the plan.

Steps to Reproduce

Click the “build” buton on a plan, I guess.

Expected Behavior

Either agent continues with the output or we have any idea to actually “review” whatever it is that it wants us to review.

Screenshots / Screen Recordings

Operating System

Windows 10/11

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.2.0-pre.23.patch.0 (user setup)
VSCode Version: 1.105.1
Commit: 0ddbd2e3ee5dabb796d837501e34beb6cf3038c0
Date: 2025-12-03T08:22:56.039Z
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.26100

For AI issues: which model did you use?

GPT-5.1 Codex Max

For AI issues: add Request ID with privacy disabled

ddd965b6-7032-4017-8b9b-19f3275d3963

Additional Information

I did have a agent review running reviewing changes in another chat, but it’s unclear if this is the review that this unrelated tab is waiting for. In either case, once that review was finished this chat tab did not proceed and is still stuck.

Does this stop you from using Cursor

No - Cursor works, but with this issue

2 Likes

Hey @Johan

Looks like you’re running on 2.2.0-pre.23.patch.0 (user setup) which is a few versions behind the latest nightly build (2.2.0-pre.28.patch.0).

To rule out any issues, since Nightly can vary in stability, can you upgrade and let us know if the problem persists? If so, shoot over a new request ID.

I got the same problem on Version: 2.2.6 (Universal) macos

Same issue here on version 2.2.17, using Sonnet 4.5 reasoning.

Version: 2.2.17 (user setup)
VSCode Version: 1.105.1
Commit: cf858ca030e9c9a99ea444ec6efcbcfc40bfda70
Date: 2025-12-11T18:30:06.649Z
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

Same issue using Opus 4.5

Version: 2.2.20
VSCode Version: 1.105.1
Commit: b3573281c4775bfc6bba466bf6563d3d498d1070
Date: 2025-12-12T06:29:26.017Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Linux x64 6.17.4-76061704-generic

Seeing this today

Version: 2.2.20
VSCode Version: 1.105.1
Commit: b3573281c4775bfc6bba466bf6563d3d498d1070
Date: 2025-12-12T06:29:26.017Z (4 days ago)
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Darwin arm64 24.6.0

I restarted my machine, and on the next run, I saw the “Accept” button, but after accepting it that time, it was again missing – no way to accept changes, so they are never implemented.

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