Cursor cannot revert back to previous prompts code

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Impossible to revert to a previous prompt’s code.
I’ve been working on multiplayer code for link cable gameplay on virtual boy.
at one point it was working decent, but i wanted more changes as we usually want… so it tried to do that. like sync shooting, taking damage etc. but after that the player’s positions didn’t update and they didn’t see eachother any more… so I explain that the multiplayer code has been broken again. so it tries to do something… then i explain again no it’s still not working…
Then I ask it to revert the last 3 prompts… Do you know what it does? it checks out from git to an really old version and starts from that… Good job Cursor!

Steps to Reproduce

  1. Make advanced adjustment you want
  2. If it breaks the previous code you wanted, ask it to fix it again
  3. Ask it to fix it again
  4. Try to revert to a previous prompt you know was working… This is not possible in cursor today.

Expected Behavior

I expect to atleast be able to go back atleast 10 prompts back. It should just be able to look through the history and revert the changes, right?

Operating System

Windows 10/11

Version Information

Version: 2.5.17 (user setup)
VSCode Version: 1.105.1
Commit: 7b98dcb824ea96c9c62362a5e80dbf0d1aae4770
Date: 2026-02-17T05:58:33.110Z
Build Type: Stable
Release Track: Default
Electron: 39.3.0
Chromium: 142.0.7444.265
Node.js: 22.21.1
V8: 14.2.231.22-electron.0
OS: Windows_NT x64 10.0.26200

For AI issues: which model did you use?

Auto

Additional Information

This is extremly annoying and has been one of my biggest annoyances with cursor.
Basically your tool is unusuable unless you git commit EVERY single change cursor does… Which you might not want to!

Does this stop you from using Cursor

Sometimes - I can sometimes use Cursor

Have you tried the Checkpoints feature? Clicking the arrow will bring you back to where you were.

I tried it just now…

It got me back to broken code somehow, but it defo wasn’t broken at that point!? So I think that functionality might actually be broken.
components/gameLoop.c: In function ‘gameLoop’:
components/gameLoop.c:900:24: error: ‘p2State’ undeclared (first use in this function)

I think it’s important to make sure the work you do between chats is standalone, if you make a small change in one chat, then in another chat do a large feature change that relies on the smaller change, and you only undo just the small change, it will leave the artifact that causes an error.

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