TBH I’d just like to remove the big Review button and the flyout that lists every file that Cursor has changed since I opened it. It doesn’t reflect the actual state of the world and stuff like that bugs me.
At least though is there a way to make it show maybe only stuff that’s been changed since the last commit? Maybe it could even reflect the actual status of the repository? As it is it’s just a list of files with annotations for how many changes Cursor has made to them since it opened and it’s pretty worthless. What is the value in “reviewing” current changes intermixed with things that are already committed?
There are code differencing and review tools that are actually easy to use, so those are my go-tos. I’ve never actually figured out what the review UI is for since I haven’t been able to make it do anything beyond reverting everything (and that was not on purpose and done without warning) and it’s also not clear to me what the function of the “commit” button is here when I got here because I wanted to review code, not commit it. (If I can’t even edit code during a review, what value is there in this UI in general?)
I understand I’m super confused at least in part because I tend to expect that tools do what they say they’re going to do… but I really just want to know how to at least make the UI that’s in my face reflect the current state of code if I’ve got to look at it.
This looks like a bug where files were piling up in the Review list. We fixed it in early January. Please update to the latest version (Help > Check for Updates) and restart Cursor.
About the Review UI: it shows the files that the Agent or Composer changed during the current chat, so you can accept or reject those changes before you commit. It is not a git diff viewer. It does not sync with git status, and it is not supposed to. After you commit, the list should clear, which is what we fixed.
You can’t disable the Review UI. It is core functionality for controlling AI changes. But if the file list clears correctly after updating, it shouldn’t get in the way.
If the issue still happens after updating, please send your Cursor version (Cursor > About Cursor > Copy), a screenshot of the Review list, and the Request ID from the latest agent run (chat context menu > Copy Request ID).
About the random full revert, that’s a separate issue. Can you describe what happened in more detail? What button did you click, and did you see any warning?
Is there any information on how you can use the UI to “control” AI changes? As far as I can tell the interface is read-only which suggests that the control is actually in further instruction to the agent?
I don’t follow what the “file list clears correctly” path is intended to be; I don’t see any way to accept or reject any changes in the UI that opens, indeed I’ve already done the accept/reject flow (and honestly would just like to automatically “accept all” since again this interface in Cursor is super clunky vs. specialized diff tools)… yet the file list persists with the count of change lines.
I don’t think a “request ID” makes sense in this case. All of the changes were accepted in Cursor and I committed them on the command line after test & review … actually at the moment (after updating Cursor) I realized that the path we were on was totally busted so I reverted everything and the file changes in the Review list persist.
Maybe the bug in this case is that the “review” UI persists even after everything has been accepted? “Controlling AI changes” has been done already, and then I commit or revert and the UI doesn’t update, hence my confusion about the purpose of this UI.
For completeness, I have now pressed the “review” button and it shows diffs that were made in a read-only window, there’s a dropdown that says “find issues” (which clearly I don’t care about) and a commit button that is disabled. I guess I just want a way to reset the “outstanding changes that need to be validated” or whatever to the new baseline. At least then at a glance I can see what Cursor has done since I hit the “ok next task” workflow… but thinking about it maybe this is where the expectation is that I’ll create a new agent with fresh context even though the current context is what I want.
