Save points and restore problems

Bug Reports
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

In the 2.0 version I found 3 annoying bugs:

  1. When a chat modify the same file a many times, I need to accept that file many times. So for example if the file was modified 3 times for 3 prompts I need to click accept 3 times at the end for a same change

  2. Rollback/restore is very strange, when I click to restore to an older point in the same chat, there are many files that are not restored and some changes are keept as if they were accepted.

  3. Restoring to a point seems to change files modified in older prompts. Example: first prompt creates a file called example.ts. the second prompt changes something else, the third prompt changes something else and updates example.ts too. When I restore to the second prompt, the example file is deleted (idk if it happens everytime, but happened here at least once)

Steps to Reproduce

Use a lot of prompts in the same chat without accepting any.
Try to accept them at the ending or restore to any point.

Expected Behavior

We should back to the save points correcly and accept the same file only once.

Operating System

Windows 10/11

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.0.75 (user setup)
VSCode Version: 1.99.3
Commit: 9e7a27b76730ca7fe4aecaeafc58bac1e2c82120
Date: 2025-11-12T17:34:21.472Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Windows_NT x64 10.0.26100

Does this stop you from using Cursor

No - Cursor works, but with this issue

2

How should it really behave in your opinion, especially in situation when modifications are in same files but for different purposes? I don’t think there is really good answer for that which covers all use cases.

3

Hey, thanks for the report. The issues with checkpoints and file acceptance are definitely serious.

To help investigate, please share:

  • Request ID: In the affected chat, click the three-dot menu (top right) > Copy Request ID
  • Console errors: When the restore issue occurs, open Help > Toggle Developer Tools > Console and share any errors
  • Auto-Run Mode: Check Cursor Settings > Agents > Auto-Run Mode - what’s your current setting?
  • Project setup: Are you using git worktrees, symlinks, or mounted drives?

Once I have the diagnostics, I can escalate this along with the related reports.

Let me know what you find.

4

1.

f93d4c04-78d9-42a1-86de-2f7b01e98140

dont remember the exact chat

3.
85cd85be-a75c-4249-9022-db1025f34268

  • Autorun - run everything
  • I use a workspace with multiples repositories (looking in the logs maybe it has some errors because of that, it tries sometimes to access my dir/workspace/rep but this path doesnt exist, the correct would be dir/rep)

here it is the logs https://drive.google.com/file/d/1v0xMm5S5IIEoFR8DKKR_gkFAe3s04w2c/view?usp=sharing

5

Thanks for the diagnostic info! The logs confirm the issue - Agent 2.0 has a path resolution bug in workspaces with multiple repositories.

What I see:

  • The Agent tries to access dir/workspace/rep instead of dir/rep (as you noted)
  • This causes Git failures, file read errors, and checkpoint/restore issues
  • All three problems come from the same path confusion

I’ll pass this to the team. It’s affecting multiple users with multi-repo setups.

Temporary workaround: open each repository in a separate Cursor window instead of a multi-root workspace. This should avoid path resolution issues while we fix the bug.

1 Like
7

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