Is this by any chance happening when creating plan files? I faced same problem with plan files only - it was fixed in some minor version of 2.4.x but now when I upgraded to 2.5.x - the problem is back… I am really getting tired of new updates breaking previous fixes. I dont mean to sound rude, kind of need to vent, but how come nobody at cursor team realizes their versioning is broken? It is happening every single update and I complained many times and so did others.
Hey, this is a known issue. The dialog shows up when the editor detects a mismatch between the file on disk and the version in the editor buffer. Here’s a quick breakdown:
What causes it: The agent writes changes to the file on disk while the editor is holding a slightly different version in memory. That mismatch triggers the conflict dialog, even if you didn’t change anything manually.
Does the model modify the file in the background: Yes. During agent sessions, especially while iterating on a plan, the agent writes directly to disk.
What to do: In most cases, choose Revert. That pulls in the latest version the agent wrote to disk. Overwrite will write the editor’s version, which might be outdated, over what the agent just wrote.
Ideally, this dialog shouldn’t appear at all if you didn’t make manual edits. The team is aware and it’s a tracked issue.
What version of Cursor are you on? Also, are you using plan mode when this happens?
