Cursor IDE showing saved files as unsaved

Support Bug Reports
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Cursor IDE is incorrectly marking previously saved files (only the ones that were actively open) as unsaved after I force-close Cursor and reopen it, or after Cursor auto-restarts during an update.

In both cases, the files were already saved and committed, but Cursor shows them as unsaved and then flags them as uncommitted/modified in Git. When I save them again, it updates the already-committed files and still treats them as changed.

Steps to Reproduce

Open Cursor IDE.

Open a few project files (ensure they are already saved and committed to Git).

Make sure these files remain actively open in the editor tabs.

Scenario A (Force close):

Force close Cursor IDE (End Task / kill process).

Reopen Cursor IDE.

Scenario B (Auto restart after update):

Update Cursor IDE to the latest version.

Allow Cursor to auto-restart after the update.

Observe that the previously opened files are now marked as unsaved.

Click Save on those files.

Check Git source control status.

Operating System

Windows 10/11

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.3.41 (user setup)
VSCode Version: 1.105.1
Commit: 2ca326e0d1ce10956aea33d54c0e2d8c13c58a30
Date: 2026-01-16T19:14:00.150Z
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

3

Hey, thanks for the report. This is a known issue: files that were previously touched by Agent or Composer get marked as changed on every IDE start. It’s usually an EOF or whitespace change, not real code.

Related reports:

This should’ve been fixed in 2.3.x, but there are reports that it came back in later 2.3.x builds.

Temporary workaround:

  1. Open Source Control
  2. Open each “changed” file
  3. If you see the “Keep” button (Agent Review overlay), click it
  4. After that, the file should stop showing up after restart

Need a bit more info:

  1. You’re on 2.3.41. Does it still happen on the latest version? Check Help > Check for Updates
  2. Can you share a git diff for one of the “changed” files? We want to confirm if it’s whitespace or EOF vs real code changes
  3. Are you using Agent or Composer modes?

Let me know what you find. If this is a regression on the latest version, I’ll pass it to the team.

4
  1. Yes. It happens on latest version, 2.3.41 and there are no updates.
  2. image
    image2019Ă—196 25.7 KB
  3. I am using Agent mode.
1 Like
5

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