[Feature Request] "Undo" feature in Cursor Compose

[tanghoong]

Is your feature request related to a problem? Please describe. As a developer using Cursor Composer, I often find myself in situations where I need to revert changes or explore previous versions of my code. Currently, there's no built-in functionality to easily roll back to a previous code version within the Cursor Composer environment. This lack of version control integration can lead to lost work, difficulty in experimenting with different code iterations, and increased time spent manually managing code versions.

Describe the solution you'd like I would like Cursor Composer to implement a code version rollback feature. This feature should:

1. Automatically save snapshots of code at regular intervals or significant changes.
2. Provide a user-friendly interface to view and compare different code versions.
3. Allow users to easily revert to a previous version with a single click or command.
4. Optionally, integrate with existing version control systems like Git for seamless workflow.

Ideally, this feature would work similarly to the "Local History" feature in some IDEs or the version history in Google Docs, but tailored specifically for code and integrated into the Cursor Composer environment.

Additional context This feature would greatly enhance the development experience in Cursor Composer by:

• Reducing the risk of losing work due to accidental changes or deletions.
• Encouraging experimentation with code, as users can easily revert if needed.
• Saving time by eliminating the need for manual backups or complex version control operations for small changes.
• Potentially integrating with AI assistance to suggest optimal versions or help in merging different versions.

A visual timeline of code versions, similar to Git's branch visualization but for local changes, could be a powerful addition to this feature.

[danperks]

Good suggestion!

In the short term, you could use Git Commits to take a snapshot of your code to revert to.

[Juand201]

Hi, this is an absolute MUST i think is a highly important feature that solves many problems and unnecesarry requests

[tanghoong]

Good suggestion!

In the short term, you could use Git Commits to take a snapshot of your code to revert to.

It happens if you work on the current git before committing, and we may keep prompting for the latest version with your codebase. If we are working on few files still manageable to revert the changes, but if there is involving on many files, revert the changes will be more tediously.