Where does the bug appear (feature/product)?
Cursor IDE
Describe the Bug
In older Cursor versions, I had a per-message “Files Changed” review panel at the end of each assistant message that only showed the edits produced by that message/turn. This made review obvious and fast.
In recent versions, that per-message panel is gone and the remaining Files Changed / Review UI shows older/stale changes (including changes from other files/past chats), which makes the review flow confusing.
What I want (key behavior)
• A review surface that shows ONLY the new changes created by the most recent assistant message/turn.
• No “old backlog” mixed in. No changes from past chats. No unrelated previously-modified files.
Why this matters
The old end-of-message panel “just made sense” because it answered one question cleanly:
“What did the assistant just change?”
The current UI often answers a different question:
“What is currently modified somewhere in this workspace / this conversation / previously?”
That’s noisy and makes it easy to accept/reject the wrong things.
Current problem (actual behavior)
• The remaining Files Changed / Review UI can show:
• previously modified files that aren’t part of the current turn
• changes from earlier prompts/turns
• sometimes even changes that feel like they belong to older chats or unrelated sessions
• Result: the review list is not reliably “this message’s edits”.
Expected behavior
One of the following:
Option A (best): restore per-message panel
• Bring back the end-of-message “Files Changed” panel, scoped to only that message’s edits.
Option B: add a toggle / mode
• Setting: “Show per-message file changes review at end of assistant messages”
• Setting or filter: “Only show changes from latest assistant turn”
• Or: “Group review items by turn” with a clear “Latest turn” group.
Steps to reproduce
1. Open workspace with existing modified files or prior change history.
2. Run an agent prompt that edits 1–2 files.
3. Open Files Changed / Review UI.
4. Observe it includes older/unrelated files or prior edits, instead of only the edits from the latest assistant message.
Impact
• Slower and more error-prone review.
• Harder to track cause/effect between message and edits.
• Breaks the tight loop of “prompt → immediate, scoped diff → accept/reject”.
Steps to Reproduce
Operating System
MacOS
Version Information
Version: 2.4.23 (Universal)
VSCode Version: 1.105.1
Commit: 379934e04d2b3290cf7aefa14560f942e4212920
Date: 2026-01-29T21:24:23.350Z
Build Type: Stable
Release Track: Default
Electron: 39.2.7
Chromium: 142.0.7444.235
Node.js: 22.21.1
V8: 14.2.231.21-electron.0
OS: Darwin arm64 25.2.0
Does this stop you from using Cursor
Sometimes - I can sometimes use Cursor