Keep All doesn't work after 22nd Aug update

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Since applying the 2 updates that were prompted today Cursor’s Keep All no longer applies the code changes. I have to brute force a Save All and then commit to Git to force the diff colours to disappear. It had all been working perfectly until these latest updates.

[Window Title]
Cursor

[Main Instruction]
Cursor

[Content]

Version: 1.5.3 (user setup)
VSCode Version: 1.99.3
Commit: aece02022292184bb34fa0c899a97928489b7b70
Date: 2025-08-22T04:48:34.365Z (12 hrs ago)
Electron: 34.5.8
Chromium: 132.0.6834.210
Node.js: 20.19.1
V8: 13.2.152.41-electron.0
OS: Windows_NT x64 10.0.26100

[Copy] [OK]

Steps to Reproduce

Do an agent request in Claude Sonnet 4 and the resulting changes can’t be applied.

Expected Behavior

It’s supposed to accept the green and red indicated changes

Operating System

Windows 10/11

Current Cursor Version (Menu → About Cursor → Copy)

[Window Title]
Cursor

[Main Instruction]
Cursor

[Content]

Version: 1.5.3 (user setup)
VSCode Version: 1.99.3
Commit: aece02022292184bb34fa0c899a97928489b7b70
Date: 2025-08-22T04:48:34.365Z (12 hrs ago)
Electron: 34.5.8
Chromium: 132.0.6834.210
Node.js: 20.19.1
V8: 13.2.152.41-electron.0
OS: Windows_NT x64 10.0.26100

Does this stop you from using Cursor

No - Cursor works, but with this issue

1 Like

Hey, thanks for the report. The team is already working on fixing it.

1 Like

any update on this?
I’m getting this issue as well… not constantly but enough.

I have multiple vs 2022 instances open looking at the same code.

Version: 1.5.11 (user setup)
VSCode Version: 1.99.3
Commit: 2f2737de9aa376933d975ae30290447c910fdf40
Date: 2025-09-05T03:48:32.332Z
Electron: 34.5.8
Chromium: 132.0.6834.210
Node.js: 20.19.1
V8: 13.2.152.41-electron.0
OS: Windows_NT x64 10.0.22631

I still get it too. A couple of the previous updates seemed to eliminate or heavily reduce the occurrences but it’s back even worse after the most recent update.
To the point now the diff only shows the green replacement and not the red removals.

Version: 1.5.11 (user setup)
VSCode Version: 1.99.3
Commit: 2f2737de9aa376933d975ae30290447c910fdf40
Date: 2025-09-05T03:48:32.332Z
Electron: 34.5.8
Chromium: 132.0.6834.210
Node.js: 20.19.1
V8: 13.2.152.41-electron.0
OS: Windows_NT x64 10.0.26100

I have a similar problem and it hasn’t been solved for exactly 30 days! - Autosave file when editing agent

After the agent changes the code, autosave does not occur!

It started after the cursor update on August 10. I did not change any settings!

Tech support, why do you even exist? You just do not respond to bug reports!

It has become very uncomfortable to work, after the agent edits the code, I have to manually resave the files!!!

1 Like

Do you have any conscience? You are brazenly ignoring an important problem! You wrote a message 17 days ago and now there is silence!

Hey, sorry, I have passed this on to the team, and they are already working on a fix that should be released in the next few days.

1 Like

What are your autosave settings? Open settings, then “File: Auto Save”

Is that question to me regarding the issue of the Keep All and Review Next file failing to work sometimes?
I have Auto Save off.

It’s always been off. I thought the point of reviewing the Cursor AI output was to decide for each file to Keep All after review and that saves the file?

The last few versions at random times after having several files updated by the Agent the Keep All on the bottom of each file does nothing as does the Review Next File button.
I have to force a save all and then commit to Git to force Cursor to get rid of the Keep All option and save the changes.

Please stop writing nonsense and giving amateurish advice! The audience here is not housewives! Autosave has nothing to do with it, it is a completely different function and it has always been disabled! Saving broke after the agent made edits to the code. It is surprising that for 2 months you have not been able to understand the essence of the problem. Do you work as a cleaner in a company or in tech support? I am not used to communicating with idiots, sorry! Do you like asking stupid unprofessional questions? Are you 15 years old?

1 Like

They’ve been explaining to him for 2 months now that autosave has nothing to do with it! I don’t even know if there’s a competent person in Cursor! It’s just amazing to disgrace yourself like that!

1 Like

The issue still persists in version 1.7.28, and I haven’t been able to find a solution so far.

I’ve tried clicking the “Keep All” and “Undo All” buttons multiple times, but nothing happens. I also attempted reloading the window and restarting Cursor, but the problem remains. What else can I do?

2 Likes

Any update on this? 1.7.33 and it still happens.

1 Like

How long is “the next few days”?
You replied 27 days ago and there have been many updates since and the issue persists.

I fixed the bug by deleting the whole Cursor cache folder, but it erased all my settings and I had to set everything up again. Not a good fix.

I have started experiencing this after the latest update, agent makes changes, files are now open in editor, they have the dot near the file name (not saved), keep all button in the editor does nothing and stays on, keep all in the chat works. given this thread, i am really considering stopping my subscription and looking for alternatives.

It still exists on 1.7.44

This is such a problem for me right now and latest updates seem to have made it worse!
Previously, I used to be able to start a new chat and that would at least clear the difs. Now, that no longer works. I’m just stuck with a ‘Keep All’ button that does nothing.

Very frustrating.

When I have a workspace, I can create a new workspace and that seems to solve the issue.

Is there anyone working on this? Any update at all?

I’m happy to share debug info!

Version: 2.0.32 (user setup)
VSCode Version: 1.99.3
Commit: 9a5dd36e54f13fb9c0e74490ec44d080dbc5df50
Date: 2025-10-29T05:23:11.655Z
Electron: 34.5.8
Chromium: 132.0.6834.210
Node.js: 20.19.1
V8: 13.2.152.41-electron.0
OS: Windows_NT x64 10.0.22631/

For what it is worth, I also have VS 2022 open at the same time.

And the files get into an unsaved state:

image

1 Like

This issue is really plaguing me right now. What also happens is that when you click “Keep All” and it doesn’t do anything (which is happening a lot lately), it messes up the undo/redo history, so that if you undo and redo, your code gets totally mangled.

1 Like

same, restarting computer and trying to update cursor plus the above mentioned attempts at fixes didn´t resolve the issue… kinda annoying