Version Control

Ideas Feature Requests
,
1

Feature request for product/service

Cursor IDE

Describe the request

Feature Request: Version History / Selective Restore for Agent Edits

Hi Cursor Team,

I’d like to suggest a feature that would significantly improve workflow safety when using agents: version control for agent-generated changes that is independent of the chat undo/keep flow.

Problem

Currently, when an agent makes multiple edits, the only available options are often:

  • Keep all changes, or
  • Undo everything.

In real usage, there are situations where I might:

  • Accidentally click Undo
  • Want to keep only some earlier edits (for example, the first 2 out of 4 changes)
  • Need to revisit a previous state after several iterations

Right now, it’s difficult to selectively restore earlier edits without losing useful work.

Proposed Solution

Introduce a version history or edit timeline for agent actions, similar to the multi-version editing experience in Gemini Canvas or Google Docs history.

Key ideas:

  • Each agent change becomes a discrete version snapshot.
  • Ability to view a timeline of edits.
  • Option to restore or branch from any previous version.
  • Support partial acceptance (e.g., keep versions 1–2 but discard 3–4).
  • Versions persist even if the chat state changes.

Example Use Case

An agent performs 4 sequential edits:

  1. Refactor imports
  2. Improve function naming
  3. Change logic structure
  4. Add experimental optimization

If edit #4 causes issues, I should be able to revert to version #2 directly — without losing earlier useful improvements.

Benefits

  • Prevents accidental loss of good edits
  • Encourages experimentation with agents
  • Reduces friction during iterative development
  • Makes Cursor feel more like a safe collaborative coding environment

I believe this would make agent workflows far more flexible and robust.

Thanks for considering this!

Screenshot / Screen Recording

Screenshot 2026-02-20 at 1.22.45 PM.png
Screenshot 2026-02-20 at 1.22.45 PM.png388×855 30 KB

Operating System (if it applies)

MacOS

3

This feature request matches a concrete problem I hit on Cursor IDE under Windows:

When I accept Agent changes via Keep/Apply, the file updates on disk but no new Timeline / Local History entry is created. A Timeline entry appears only after a manual Ctrl+S in the editor. This makes agent-driven iterations hard to audit/rollback unless you constantly remember to save manually.

I filed a reproducible bug report with full repro steps + version info here: Agent file edits do not create a Timeline/Local History entry.

If Cursor created a Local History checkpoint on Keep/Apply (or triggered an editor-level save that is recorded by Local History), it would solve a big part of the “version control for agentic changes” safety problem, even for users without git.