Old "Edited Files" from week ago still stuck to "Duplicate Chat" conversation copies

Bug Reports
1

Hello!

I have a conversation where in the MIDDLE of an old conversation, I do a “Duplicate Conversation” to create a short dense-context conversation from an excellent bootstrap conversation template in Cursor.

The Good:

Fantastic feature Windsurf doesn’t have!
The ability to fork an existing chat from an earlier point of an existing chat:

A new chat that is a copy of an existing conversation – but rewinding a conversation partially. This is useful when you need a small amount of quick bootstrap context (e.g. 1-3 chat turns worth, ignoring the 15 chat turns after), but don’t want to re-explain things all over again to chat.

image
image159×152 5.11 KB

The Minor Problem:

But there’s one bug. It perpetually and permanenttly has an undismissable old changelog attached:

image

But those files are now descended far beyond (many edits since). And those are changed files from a later point in that specific conversation.

How do I delete the “Edited 2 files” part when cloning/forking an old conversation that has fantastically useful history. It shows changelog from almost one week ago.

How do I clear/flush/delete the “Edited 2 files +79 -6” part, when I’m forking template conversations? It’s pretty useful to ask new questions from an already context-filled conversation introduction (e.g. clear task). The edited files got accidentally attached, and is irrelevant to the template (unrelated conversation history anyway), so this is a cosmetic bug at this stage…

Even as I continue chat, it persistenty stays that way, even when I continue to edit the file, move the file, delete the file, or even try to “accept” the changes (nothing happens). So a cosmetic annoyance at the moment; which feels like a bug.

It’s completely impossible to dismiss. Expanding the files + clicking on the files does not reapply the changes, nothing happens, so it persistently stays in an undismissable manner).

(Not showing filenames, as they’re a bit of a trade secret in filenames, but I can try to reproduce using generic files in a blank project, if you need reproduction steps).

2

Let’s see…

Steps to Reproduce Bug

  1. Start a new conversation that will become a great template for “Duplicate Chat” contexts.

“I’m new to Cursor. Study my project, including also @README.md, @Project.PDF and my project source code folder structure. Tell me what my existing project does. Impress me!” (or similar bootstrap query that takes 1 minute for Cursor to do, that educates far beyond index system)

  1. Continue the same chat, and ask it to do some code changes. You’ll have a “Edited X files” pop up.

  2. Ignore that for now, continue a few chat rounds (back and fourth questions).

  3. Scroll up to Cursors’ answer to the first query (e.g. first reply by Claude Sonnet 4), click the […] at bottom-right corner of the first or second reply, and then do a “Duplicate Chat”

  4. The “Edited X Files” will kind of permanently duplicate over, everytime you fork from that conversation point.

  5. This occurs even if you’ve long edited/accepted/rejected/etc in the original conversation (but not the forked conversations). Try random permutations based on this to reproduce the bug.

In some permutations, all forked conversations now get ‘stuck’ with these “Edited X Files” that are impossible to dismiss/impossible to accept/impossible to reject/permanently stuck.

There are other kinds of bootstrap conversations where conversation forking and code-exampling is useful (e.g. teaching conversations such as “Teach me ACME Toolit API”), that allows me to fork a Chapter3-specific conversation without context pollution of a Chapter2-specific conversation.

Keeping context windows small via mid-chat-history “Duplicate Chat” trick (new conversations that rewinds old conversations) is a very clever Cursor feature, so compliment for that. Just a cosmetic side effect to fix.