Originally published on DebugRadar.
Quick Fix Summary
- Problem: Cursor 3.29 leaves a "Keep all changes" / "Review Next File" review bar pinned to the top-right of the editor with no way to dismiss it — and it comes back after you accept new Agent diffs. Clicking Keep is a silent no-op when the file no longer exists.
- Fix: It is a stale review state from a file that no longer exists. Safest first try: recreate the file at its exact deleted path, click Keep all changes, then delete it again. If that fails, delete
state.vscdb(back up first, quit Cursor first) or clean the stale rows with SQL. - What happened: First reports November 10, 2026 (Cursor 3.29.15, 3.29.16), multiple confirmations November 10–11. Cursor staff confirmed on November 11 that it is a known issue that started in 3.29, with no fix shipped yet.
Technical Root Cause
| Error Code | Affected Version | Root Cause | Current Status |
|---|---|---|---|
| No error code — UI-state bug | Cursor 3.29.x (3.29.15, 3.29.16 reported), Windows + macOS | Stale review state — the bar belongs to a pending Agent change on a file that no longer exists (deleted git-tracked file / removed worktree / agent temp file). Staff (Colin, Nov 11, 3:31pm) confirmed: "This is a known issue the team is aware of, and it's recent: it started showing up on 3.29." | Still open as of Nov 11, 2026 — first reports Nov 10, multiple confirmations Nov 10–11. Note honestly: the reports are from Nov 10, about 5–6 days old at publish; the symptom class recurs in older threads, but the 3.29 regression is new |
Step-by-Step: What to Do When Cursor's Review Bar Won't Dismiss
Step 1 — Try the Staff Suggestion First
Recreate the folder/file at the exact deleted path, click Keep all changes, then delete the folder again. This is the staff suggestion — it clears the stale review state without touching Cursor's local database.
Step 2 — Delete state.vscdb (Back Up First)
If the bar survives Step 1, quit Cursor, back up, then delete state.vscdb + state.vscdb.backup (macOS user-verified). This wipes Cursor's local state, so back it up first and quit Cursor before deleting. It is a user-reported workaround, not an official fix.
Step 3 — Clean the Stale Rows With SQL (Advanced)
For the precise fix, delete the stale inlineDiff:<workspaceHash>:% rows from the cursorDiskKV table in %APPDATA%\Cursor\User\globalStorage\state.vscdb via SQL (forum thread 177884). Advanced — back up the file first, and quit Cursor before editing it.
Step 4 — Keep a Backup AI Coding Assistant Ready
While Cursor's review UI is stuck, a second AI coding assistant keeps you shipping. If the bar blocks your editor, your code and your context should live somewhere that survives a Cursor restart — a committed repo and a second editor, not one long-lived Cursor session.
While Cursor's review bar is stuck, keep a second AI coding assistant: A stuck bar should not end your workday. GitHub Copilot runs in your editor as a second AI coding assistant, so you can keep writing and reviewing code while Cursor sorts out the 3.29 review bug. (Affiliate link — DebugRadar earns a commission if you sign up through it.)
The same discipline applied to the Cursor crash we covered in Fix: Cursor Crashes With 0x80000003 Error — when the vendor has to fix it, your job is evidence and a workaround, not a fake fix. And the same pattern showed up in the GitHub Copilot model outage in Fix: GitHub Copilot Models Not Working — check the vendor's status first, then work around it.
FAQ
Why won't the 'Keep all changes' bar go away?
It is a stale review state: the bar belongs to a pending Agent change on a file that no longer exists — a deleted file or a removed worktree. Cursor 3.29 keeps showing it because the review state was never cleared.
Is deleting state.vscdb safe?
It wipes Cursor's local state, so back it up first and quit Cursor before deleting. It is a user-reported workaround, not an official fix — the safer first try is recreating the deleted file at its exact path, clicking Keep all changes, then deleting it again.
Did Cursor fix this yet?
No. Cursor staff confirmed on November 11 that it is a known issue that started in 3.29, with no fix shipped yet. The workarounds above clear the stuck bar on your machine.
Sources: Cursor forum thread, "Persistent 'Keep all changes' / 'Review Next File' bar in the editor cannot be dismissed, it returns after accepting new Agent diffs (3.29.15)", November 10, 2026 (https://forum.cursor.com/t/persistent-keep-all-changes-review-next-file-bar-in-the-editor-cannot-be-dismissed-it-returns-after-accepting-new-agent-diffs-3-29-15/177925); Cursor forum thread, "Stale 'Keep all changes' review UI after worktree removal, button is a silent no-op", November 10, 2026 (https://forum.cursor.com/t/stale-keep-all-changes-review-ui-after-worktree-removal-button-is-a-silent-no-op/177884).
Read the full guide on DebugRadar: Fix: Cursor 'Keep All Changes' Bar Won't Go Away