Critical Data Loss After Reverting to Cursor 1.2

Describe the Bug

The latest update removed the “Revert Changes” functionality for me, so I decided to roll back to version 1.2. After doing so, the chat I had open replaced the code in several files where Cursor had previously made changes, with only the modifications made by Cursor, effectively erasing hours of my work that hadn’t yet been pushed to GitHub. This was incredibly frustrating and set me back by about six hours.

Issues like this cannot be allowed to happen. There needs to be stronger version control built into the system.

To make matters worse, after reverting to Cursor 1.2, I can no longer access my previous chats—they’re stuck loading and eventually redirect to a blank new chat.

Steps to Reproduce

  1. Have a chat with cursor.
  2. Downgrade cursor version.
  3. Open the files changed by cursor in the previous chat.

Expected Behavior

It’s not supposed to delete all other code in the files modified by Cursor. I understand this is a bug, but if Cursor had proper version control for its chats, this wouldn’t have been an issue.

Operating System

Windows 10/11

Current Cursor Version (Menu → About Cursor → Copy)

Version: 1.2.1 (user setup)
VSCode Version: 1.99.3
Commit: 031e7e0ff1e2eda9c1a0f5df67d44053b059c5d0
Date: 2025-07-03T06:16:02.610Z
Electron: 34.5.1
Chromium: 132.0.6834.210
Node.js: 20.19.0
V8: 13.2.152.41-electron.0
OS: Windows_NT x64 10.0.22631

Does this stop you from using Cursor

Yes - Cursor is unusable

This topic was automatically closed 22 days after the last reply. New replies are no longer allowed.