Cursor randomly reverts code without consent

[Justin_Thomas]

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Cursor IDE contains a catastrophic bug that randomly reverts file contents without user consent, notification, or warning. This results in silent data loss, destroyed productivity, and broken trust in the tool.

The Problem

During normal development with Cursor’s AI features, files are randomly reverted to previous states. This happens:

• Without any warning or notification
• Without user action or consent
• After changes have been successfully saved
• Across multiple file types and sizes
• Both for AI-generated and manually typed code

What Gets Reverted

• Complete files - Entire files reduced to empty or near-empty state
• Partial changes - Specific edits undone while other changes persist
• Multiple files simultaneously - Several files revert at the same time
• Recent work - Changes made minutes ago simply disappear

So.. Cursor wants to remove unlimited auto requests while simultaneously their product is unusable? Classy.

Side note. Noticed another forum members post on the same issue that was happening a month ago. Still not fixed huh?

Steps to Reproduce

Use auto mode, code like normal, watch your work disappear. Rinse and repeat.

Expected Behavior

For it to not revert code without my consent?

Operating System

MacOS

Current Cursor Version (Menu → About Cursor → Copy)

Version: 1.7.52 (Universal)
VSCode Version: 1.99.3

For AI issues: which model did you use?

Auto

Does this stop you from using Cursor

Yes - Cursor is unusable

[deanrie]

Hey, thanks for the report. I understand this is really frustrating, especially with the recent unlimited auto changes.

This looks similar to a known issue where stopping Agent operations can revert changes.

To help us investigate your case:

• Can you share a request ID from when this happened? (Three dots in chat → Copy Request ID)
• Does this happen when you click “stop” during Agent operations, or at random times?

Immediate workarounds:

• Try Timeline view (right‑click file → “Open Timeline ") to restore reverted changes
• Use Checkpoints, click “Restore Checkpoint” on previous Agent requests
• Commit to Git frequently, especially before clicking stop or starting new Agent tasks

From similar reports, committing to Git after each Agent task has been the most reliable workaround until this is fixed.

[Andreul369 (Andreul-)]

I solved some bugs at a point in time. Then I continued my work, and at some point I remembered about an old conversation in Ask mode and went to that old conversation and sometimes the old bugs were back in my code. I honestly thought I’m losing my mind.

[Justin_Thomas]

If I do so can I somehow get extra credits or something?. I can’t use your Auto mode and am forced to use specific models. Half of which don’t even work themselves. Can’t use any Claude Model.”From similar reports, committing to Git after each Agent task has been the most reliable workaround until this is fixed.” Is not a a solution. Kept getting another error. (Can’t remember what it was but I’m already at my usage limit for the month), I’ve basically been forced to used heavier models due to trying to doge Cursors bugs. By principle alone I refuse to enable on demand usage or increase my plan.

And for the love of god, can you guys focus on fixing these bugs before adding extra features to Cursor? Which will probably have its own bugs. Saw some new features added within the past couple days. Honestly I’m dumbfounded they’ve been added when half your models dont work.

You guys need to be able to provide your base service for your Pro plan, otherwise it’s basically like I’m just paying $20 p/m for the privilege of using vscode. Don’t let this app become a scam please.

Update:
Even as we speak, I just tried to see if I could use “auto” mode to get the requested information and the all I get is “We’re having trouble connecting to the model provider” 89fe8a35-bc70-4e25-b4e1-08b847b76200 which is another bug its self. I can’t even use your bugged out model now.