Revert / Restore last set of changes "Broken:

Revert / Restore last set of changes "Broken:

Hello Cursor Team,

Our team is currently engaged in the development of a game utilizing this code editor. Previously, when the AI deleted specific items, we relied on the Revert/Restore last set of changes feature, which functioned effectively. However, following the recent update, this feature is no longer operational, resulting in the loss of game files. Consequently, we have experienced a complete loss of our game, leaving us uncertain about the next steps to take, as the situation has deteriorated to the extent that we have lost our progress. We are utilizing the agent composer mode, and unfortunately, the Revert/Restore last set of changes feature is ineffective in this latest update.

Thanks, AlphaMeld Game Dev

2 Likes

Hey, which version of Cursor are you using?

Version: 0.44.5
VSCode Version: 1.93.1
Commit: 1d610252e6812bf33245763f0742a534fd0f1d90
Date: 2024-12-20T00:02:28.554Z
Electron: 30.5.1
Chromium: 124.0.6367.243
Node.js: 20.16.0
V8: 12.4.254.20-electron.0
OS: Windows_NT x64 10.0.19045

I am also experiencing the same issue with the missing Compose mode

Same. I am having to resort to the file Timeline to restore. :frowning:

I have two physically identical laptops - win10 & win11 respectively., and I have 44.5 installed on both - I updated both to 44.8

win10 44.8 has composer in ctrl+L

win11 44.8 does not have composer at all in ctrl+L only Chat.

We have also found out that when we go and restore by doing ctrl + Z / ctrl + Y that doesn’t work either to restore / revert file changes. So DEV what can we do form here to restore our game we are building? Please let us know!

I have an idea:

talk with @gregce – he created the SpecStory Cursor extension…

Work with him directly - to have all your team install this extension and capture as much composer history as possible. Pipe all the composer output to a DB, postgres whatever… get as many artifacts as you can from timeline, whatever repo’s you have. Check versioning on github…

And then point all your composer agents at the problem.

Maybe CrewAI would be a good thing to coordinate a custom agent swarm onto your histories.

Also - you need to set a rules environment that you obsessively duplicate and backup.

I cant belive you dont have versioning?


Ive been doing extensive testing on wrangling Composer Agents to contunuously document their activities for these reasons.