# Dummy changes for review

**URL:** <https://forum.cursor.com/t/dummy-changes-for-review/176464>\
**Category:** Bug Reports\
**Tags:** review\
**Created:** [October 28, 2026, 8:00am UTC](https://forum.cursor.com/t/dummy-changes-for-review/176464 "2026-10-28T08:00:07Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Ofer\_Ebert](https://avatars.discourse-cdn.com/v4/letter/o/9fc348/32.png) [@Ofer\_Ebert](https://forum.cursor.com/u/Ofer_Ebert)\
**Post date:** [October 28, 2026, 8:00am UTC](https://forum.cursor.com/t/dummy-changes-for-review/176464/1 "2026-10-28T08:00:07Z")

</div>

### Where does the bug appear (feature/product)?

Cursor IDE

### Describe the Bug

Agent Review showed 22 approvals for 7 real hunks in application.py  
Unchanged surrounding lines painted green / required Keep  
After undo + clean re-apply, the same edit correctly showed 7  
This cause me to waste my time reviewing 15 dummy changes

### Steps to Reproduce

I do not know

### Operating System

Windows 10/11

### Version Information

Version: 3.21.18 (user setup)  
VS Code Extension API: 1.128.0  
Commit: c4730f7d93d787d9ab120af715999f0345ee5bc0  
Date: 2026-09-22T02:04:34.641Z  
Layout: IDE  
Build Type: Stable  
Release Track: Default  
Electron: 42.10.0  
Chromium: 148.0.7778.280  
Node.js: 24.18.1  
V8: 14.8.178.38-electron.0  
xterm.js: 6.1.0-beta.291  
OS: Windows\_NT x64 10.0.22631

### For AI issues: add Request ID with privacy disabled

e6113b20-5592-44f5-83b3-4b0c1ffd6cd9

### Does this stop you from using Cursor

No - Cursor works, but with this issue

---

<div class="post-metadata">

**Author:** ![Colin](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/colin/32/90452_2.png) [@Colin](https://forum.cursor.com/u/Colin)\
**Post date:** [October 28, 2026, 10:50am UTC](https://forum.cursor.com/t/dummy-changes-for-review/176464/6 "2026-10-28T10:50:09Z")

</div>

Hi @Ofer_Ebert,

The extra hunks most likely weren’t new changes from this edit. The review can end up comparing against an older version of the file, so changes still waiting for Keep/Undo from earlier turns in that chat, or anything else that touched the file while the agent was running (format-on-save, a formatter, a manual edit), get counted as part of the agent’s diff. That would explain why undo and re-apply showed the right 7.

To avoid it for now:

1. Keep or Undo a file’s pending changes before the next request that edits it, especially in a chat you’ve used over several days.
2. Avoid saving or formatting that file while the agent is working on it.
3. When a count looks off, check Source Control to see what actually changed.

Did application.py already have pending changes from earlier in that chat, or did something else touch it during the run? That tells us which case you hit.