Updated a different file than the one in the editor

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Hey there,

I am using the new 2.0, and this bug just happened to me. I asked it to change a file, and instead of the changes diff appearing in the file I was in, it appeared in an identical file with the same path, but the IDE opened it as a different tab. In the original tab, the changes do appear, the diffs don’t appear, and the button at the bottom says Review next file. Note that GPT-5 did not create the file; I had already created it, and it just edited the file.

Aslo note that I have been using Cursor with the exact same settings multiple times today without any issues.

The original file just shows the following path in the top:
src > components > waiting-room > side-panel > settings.tsx
While the file with the diffs shows the entire one from my drive.

I think it makes more sense when you see the screenshot (can only upload one).

Steps to Reproduce

As mentioned, it only happened for this one generation so far, but just ask it to edit any file.

Screenshots / Screen Recordings

Operating System

Windows 10/11

Current Cursor Version (Menu → About Cursor → Copy)

Couldn’t find Menu → About Cursor, but I just updated to 2.0.

For AI issues: which model did you use?

GTP-5 Codex

For AI issues: add Request ID with privacy disabled

e68843ba-6b57-4a42-9b8f-3f17744603dc

Does this stop you from using Cursor

No - Cursor works, but with this issue

Hey, thanks for the report. This looks like a path-handling issue in Cursor 2.0: the diff opens in a duplicate tab with the full path instead of showing in the original relative-path tab.

I’ll pass this to the team. Since the changes appear in the original file but without the diff, you can keep working, accept or reject changes from the duplicate tab when it happens.

Let me know if this becomes more frequent or if you notice a pattern that triggers it.

Hey, thanks for the quick reply.

Currently, it has only happened in two chats and was fixed by starting a new chat. And yes, it is just a very minor inconvenience, the few times it happens. Just thought I would report it, if others are experiencing something similar.

It hasn’t happened today, but I’ll be sure to let you know.

Thanks.

1 Like