After the agent completes changes across multiple files, the bottom review bar (with “Keep All” / “Reject All” and the file-by-file navigation — “Next File” / “Previous File”) no longer appears. Previously this bar showed up automatically after every agent run, allowing me to step through each changed file and review diffs before accepting.
Now the changes are applied silently and I have to manually hunt through the file tree or run git diff to find what was modified. The per-file review workflow is completely gone.
This was reported previously in Agent mode no longer shows review/accept interface and Only some diffs are shown when agent makes changes, but both threads were auto-closed without a fix.
Steps to Reproduce
Steps to Reproduce
Open a multi-file project
Use Agent mode to make changes that touch 2+ files
Wait for the agent to finish
Observe: no review bar appears at the bottom, no “Next File” / “Keep All” controls, changes are auto-applied
Expected Behavior
After agent completes, the bottom review bar should appear with:
“Keep All” / “Reject All” buttons
Per-file navigation (“Next File” / “Previous File”)
Per-file “Keep” / “Reject” controls
Diff highlights in the editor for each changed file
Here are a couple of workarounds that helped others:
Try toggling Inline Diffs: Cursor Settings > Agents > Inline Diffs - turn it off, then back on, and restart Cursor.
Before each agent run, make a git commit. If something goes wrong, you can always roll back with git checkout -- . or git stash. It’s not perfect, but it works as a safety net.
For reviewing changes, you can use the Review panel in the sidebar or git diff in the terminal.
Thanks for the response, but I have to be honest… this is getting hard to accept.
This bug was first reported in October 2025. It’s now late March 2026. That’s five months of a core workflow being broken, with “the team is aware” being the only update. The linked thread was auto-closed without resolution, and now this one will likely meet the same fate.
The review bar isn’t some nice-to-have… it’s the primary mechanism for reviewing agent changes safely. Without it, the agent just silently modifies files across the project and you’re left playing detective with git diff. That’s not a workaround, that’s a regression to a pre-AI workflow.
“Toggle Inline Diffs off and on and restart” is not a fix. “Make a git commit before each agent run” is not a fix. These are band-aids for a feature that worked perfectly fine until an update broke it.
For a product charging $200/month on the premise that AI-assisted development is safe and productive, shipping an update that removes the ability to review AI changes, and then leaving it broken for months, is a pretty serious oversight. This should be treated as a P0, not a “known issue, no ETA.”
Can we get an actual timeline on this? Or at minimum, confirmation that it’s actively being worked on rather than sitting in a backlog?