Agent Review Loop Bug still not solved

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

When using the “Verify these issues exist and fix them” feature, Cursor’s agent review system automatically deletes previously accepted changes, even after they have been committed and pushed to git. This creates a regression loop where the same fix needs to be re-applied multiple times.
Steps to Reproduce
Agent makes code changes (e.g., adds a field to a JavaScript array)
// Agent adds this line: { key: ‘liefer1_adresse’, icon: ‘fa-map-marked-alt’, label: ‘Adresse Details’ },
User accepts the changes via the “Accept” button in the diff view
Changes are committed and pushed to GitHub
git add templates/auftragsmanagement.html git commit -m “Fix: Add liefer1_adresse field” git push
User triggers agent review with: “Verify these issues exist and fix them: Bug 1: The field liefer1_adresse is missing…”
BUG: The previously accepted change is automatically deleted from the working copy

  • { key: ‘liefer1_adresse’, icon: ‘fa-map-marked-alt’, label: ‘Adresse Details’ },
    Expected Behavior
    Agent review should verify that the field exists (since it was already added and committed)
    No automatic deletion of previously accepted and committed changes
    Agent should report: “:white_check_mark: Field exists, no fix needed”
    Actual Behavior
    Agent review automatically deletes the previously added line
    The deletion happens silently without user confirmation
    Agent then “fixes” the issue by re-adding the same line
    Creates a regression loop: Add → Accept → Commit → Review deletes it → Add again
    Impact
    Regression Loop: Same fixes need to be applied multiple times
    Git History Pollution: Multiple commits for the same fix
    User Confusion: “Why was my accepted change deleted?”
    Workflow Disruption: Wastes time re-applying identical changes
    Environment
    Cursor Version: [Current Cursor version]
    OS: Windows 10 (Build 26200)
    Git: Working with remote repository on GitHub
    Agent Model: Claude Sonnet 4.5
    File Type: HTML template with embedded JavaScript
    Workaround
    Currently, we manually re-add the deleted changes after each agent review cycle and commit again.
    Root Cause (Hypothesis)
    The agent review system appears to:
    Compare the current working copy against some cached/previous state
    Generate a “fix” based on that comparison
    Automatically apply deletions without checking git history or user acceptance state
    Not respect previously accepted changes or committed code
    Suggested Fix
    Agent review should only suggest changes, not automatically delete existing code
    OR: Agent review should check git history before suggesting deletions
    OR: Agent review should respect user’s “accepted changes” state
    OR: Add a confirmation dialog before deleting previously accepted changes
    Reproduction Frequency
    Consistent: Happens every time we use “Verify these issues exist and fix them” on code that was previously modified by the agent
    Severity: High - disrupts normal development workflow

Steps to Reproduce

Steps to Reproduce
Initial Chat: Start a conversation with the agent
User: “Add field liefer1_adresse to the zustellungSection array”
Agent implements change:
// File: templates/auftragsmanagement.html // Agent adds this line at position 1104: { key: ‘liefer1_adresse’, icon: ‘fa-map-marked-alt’, label: ‘Adresse Details’ },
User accepts the change:
Click “Accept” button in the diff view
File is modified in working copy
Changes are committed and pushed:
git add templates/auftragsmanagement.html git commit -m “Fix: Add liefer1_adresse field” git push origin main
Push completes successfully:
GitHub shows the commit with the added line
Working copy and remote are in sync
User triggers agent verification (in the SAME chat session):
User sends message: “Verify these issues exist and fix them: Bug 1: The field liefer1_adresse is missing from zustellungSection”
OR User uses the @ selection feature to highlight a code section and requests verification
BUG OCCURS:
Cursor’s agent review system automatically deletes the previously added line from the working copy
The deletion happens without user confirmation
The deletion happens despite the change being accepted and committed
User sees the diff marker showing the deletion:
- { key: ‘liefer1_adresse’, icon: ‘fa-map-marked-alt’, label: ‘Adresse Details’ },
Agent “fixes” by re-adding the same line:
Agent detects the field is missing (because it was just auto-deleted)
Agent adds the exact same line again
Cycle repeats

Expected Behavior

Agent review should verify that the field exists (since it was already added and committed)
No automatic deletion of previously accepted and committed changes
Agent should report: “:white_check_mark: Field exists, no fix needed”

Operating System

Windows 10/11

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.0.69 (user setup)
VSCode Version: 1.99.3
Commit: 63fcac100bd5d5749f2a98aa47d65f6eca61db30
Date: 2025-11-07T18:21:29.650Z
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

For AI issues: add Request ID with privacy disabled

14223a5e-7d20-4558-824d-1dad99fb277e

Does this stop you from using Cursor

No - Cursor works, but with this issue

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

The new review feature obfuscates current changes.

Steps to Reproduce

1 Prompt and accept changes, staging/committing so there are no visible changes
2 Use the same thread to create new changes.
THEN
3a Click the review button and note previously accepted changes are also pressent in the review tab (BUG expect only to see current changes)
OR
3b Click a file to review the file and note the Review tab is opened (BUG expect file to open in tab or file tab to be focused)

Expected Behavior

3a (BUG expect only to see current changes)
3b (BUG expect file to open in tab or file tab to be focused)

Operating System

MacOS

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.1.17
VSCode Version: 1.105.1
Commit: 6757269838ae9ac4caaa2be13f396fdfbcf1f9a0
Date: 2025-11-21T08:55:17.983Z
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.3.0

Does this stop you from using Cursor

No - Cursor works, but with this issue

Hey, thanks for the report. This is a serious issue and it definitely shouldn’t be happening. Accepted and committed changes should not be automatically deleted by Agent Review.

I’ll pass this on to the team.

Quick question to help the team: does this regression loop happen only when you use “Verify these issues exist” in the same chat where you originally made the changes, or does it also occur in a new chat?

Temporary workaround: until this is fixed, try running the review in a new chat after making changes, as this may help avoid the deletion behavior.

@deanc your report about Review showing previously committed changes is related to this problem. The team will investigate both issues together.

Hello

This bug persists also in new chat after my knowledge.

The current workaround is to immediately close review agent, (hit x on left side panel for issue) once I have sent verify this issue exists in chat. With that, the review agent cannot delete changes anymore.

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