After clicking Review in Agent chat for already-committed changes, Cursor still allows commit flow and ends with “There are no changes to commit.”

Support Bug Reports
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

After agent changes have already been committed, clicking Review in Agent chat opens a review flow where the Commit button is still enabled.

When that first Commit button is clicked, it does not immediately show a warning. Instead, it opens the commit dialog with selected files and an auto-generated commit message. After that, clicking the second Commit button in that dialog shows “There are no changes to commit.”

Post-commit review may be intentional, but the enabled commit flow is misleading in this state. If there are no pending changes, the UI should clearly indicate that (for example, “Already committed” / “No pending changes”) and disable or replace commit actions, rather than allowing users to proceed through commit UI steps that predictably end in this warning.

This adds inconvenience because it is unclear whether prior changes were actually committed and whether it is safe to start a new task. The current behavior introduces uncertainty and extra verification steps in normal workflow.

Steps to Reproduce

  1. Let an agent complete changes and commit them (or otherwise ensure the changes are already committed).
  2. In Agent chat, click Review.
  3. Click the first Commit button shown from the review state.
  4. Observe that Cursor opens a commit dialog with selected files and an auto-generated commit message.
  5. Click the second Commit button in that dialog.
  6. Observe warning: “There are no changes to commit.”
  7. Run Developer: Reload Window and repeat — issue still persists.

Expected Behavior

If the reviewed changes are already committed, the UI should clearly indicate no pending changes and disable/replace commit actions, rather than allowing users through commit UI steps that predictably fail.

Operating System

MacOS

Version Information

IDE: 2.4.37 (Universal)

Does this stop you from using Cursor

No - Cursor works, but with this issue

1 Like
3

Hey, thanks for the report.

This is a known issue with how the Review UI syncs state with Git. The Commit button stays enabled even after the changes are already committed. The team is aware of this bug. It’s related to the UI not refreshing after the agent runs Git commands.

Your detailed report with clear steps helps a lot, especially the part where the UI goes through the full commit flow instead of showing a warning right away.

There’s no workaround yet, but you can run git status in the terminal before clicking Review if you’re not sure whether everything is already committed. Let me know if you find anything else related to this.

1 Like
4

I’m confirming I encounter exactly this situation. While the Cursor folks are working on a fix, it will be nice to provide us with a way to manually reset the view. I tried:

  • restarting Cursor;
  • Developer: Reload Window

but it didn’t help.