Pressing ‘Keep’ floods active editor with clipboard spam and corrupts file contents and sometime kinda freezes VS Code

[VigilanteSystems]

• Copilot Chat Extension Version: github.copilot-chat Version 0.32.3, github.copilot Version 1.383.1811
• VS Code Version: 1.105.1 (system setup)
• OS Version: Windows 10 Pro 22H2 19045.6456
• Feature (agent/edit): Copilot “Keep”/“Undo” controls for applied edits
• Selected model : any and all models show this behaviour, even my beloved grok1coder
• Logs: none, available, sorry

Steps to Reproduce:

1. Ask Copilot to apply changes that modify one or more files.
2. Leave at least one affected file open in the editor while Copilot finishes its edits. Once the “Keep / Undo” banner appears, click “Keep.”
3. Observe the still-open editor tab: the file begins filling with repeated clipboard/cache text (often Markdown fragments).
   The insertion continues until the file grows dramatically (e.g., ~100 lines → thousands), effectively hanging VS Code.
   (well not always THAT severe, but the file content becomes corrupted and if the spamming is ALOT then it really affect VSCode stability.)
   Closing all editor tabs before pressing “Keep” seems to avoid the spam, but keeping a tab open consistently triggers it.

PS:
one caveat, i have not yet tested if this behaviour only (like ONLY) shows when the last action copliot did, was to create or edit a markdown file, that is too microstepping for me for this really annoying "feature"(??).. i still think its a bug!
Thanks and godspeed!

[jrieken]

Observe the still-open editor tab: the file begins filling with repeated clipboard/cache text (often Markdown fragments).
The insertion continues until the file grows dramatically

This can only mean the request/agent has finished yet. The "Keep" command is just about removing decorations for added code, it doesn't change any code. Looks like @connor4312 allowed to press keep while the request is still running (see #255464) so I leave it up to him

[VigilanteSystems]

Cool, so its rather a workflow bug on my side and the button will be removed anyway, no need to keep pressing it?

[jrieken]

Unsure what has been discussed about its future but "Keep" just means acknowledging the changes which have already been made. So, its implementation just removes decorations and "Undo" is the "doer", remove the AI changes. Tho, its other use is that it tracks the kept state as "good" and one to potentially go back to.

[connor4312]

/gifPlease

[vs-code-engineering]

Thanks for reporting this issue! Unfortunately, it's hard for us to understand what issue you're seeing. Please help us out by providing a screen recording showing exactly what isn't working as expected. While we can work with most standard formats, .gif files are preferred as they are displayed inline on GitHub. You may find https://gifcap.dev helpful as a browser-based gif recording tool.

If the issue depends on keyboard input, you can help us by enabling screencast mode for the recording (Developer: Toggle Screencast Mode in the command palette). Lastly, please attach this file via the GitHub web interface as emailed responses will strip files out from the issue.

Happy coding!

[VigilanteSystems]

i have to switch to other file view/editor to stop the spamming, as you can see, this time it realized directly something is off with the file, often it doesnt realize it only after the fact.
now i do, first i close all open editors, Ctrl+W is my friend, then press "Keep" button.
anyway here is the gif: (sorry, i have made a 2+GB gif from my 8MB mp4 file, so here you have the YT link:
https://youtu.be/-yoBK3clxFU

PS:
The times i click the close-X on the spammed tab, the OBS didnt record the "Saveme?" dialog, i tried to save and the other, except cancel nothing happened, the unsaved state doesnt change too

[connor4312]

I have never seen that before. I suspect there might be some extension causing this somehow. I suggest trying to create a new profile without your existing extensions and add copilot in. (Or just manually disable current extensions.) See if it happens there, and if not, add some extensions back until you see it happen.