Hey, this is a known issue. Files get modified because Agent Review state is restored when Cursor starts or updates. It’s usually whitespace or line-ending changes in files that Agent or Composer touched before.
Your report duplicates the main thread: Cursor modifying files on startup 2000+ views, 60+ posts. The team is aware, but there’s no fix released yet. The issue has persisted from 2.0.x through the current 3.1.x.
Workarounds from other users:
Open each file from the review list, then click Keep or Undo File, then Review next file, repeat for all files
Stage all changes in git, then unstage
Reset to the last commit after each restart
To help with debugging, if you want:
Share a git diff for one of the files. Are the changes real code changes or only whitespace and newlines?
Your git config core.autocrlf value
Your list of installed extensions, especially formatters
Hey @redstar quick update on the phantom unsaved changes issue. Part of the problem, where files show up as modified or unsaved even though the content on disk is the same and re-saving doesn’t help, was fixed in a recent build. Please update to the latest version and check if the phantom changes are still there after a restart or upgrade.
Separately, we’re still looking into the case where files get written to disk on startup, like mtime or EOL changes on untouched files. No exact ETA for that yet.
If after updating you still see files actually changing on disk, please share:
git diff for one of the files are there real code changes or only whitespace or newlines?
your git config core.autocrlf value
a list of installed extensions, especially formatters