Responding with a follow-up when AI suggests an edit results in desync

[mcendu]

Before submitting your bug report

• I've tried using the "Ask AI" feature on the Continue docs site to see if the docs have an answer
• I'm not able to find a related conversation on GitHub discussions that reports the same bug
• I'm not able to find an open issue that reports the same bug
• I've seen the troubleshooting guide on the Continue Docs

Relevant environment info

- OS: Windows 11
- Continue version: 1.2.22
- IDE version: Code 1.117.0
- Model: "DeepSeek Coder" (deepseek-v4-flash)

Description

When the AI requests an edit, you can type in a follow-up instead of rejecting or accepting the edit. The edit request will not be carried out, but the AI will receive an indicator that the edit was successful. As a result, the AI's view of the file will disagree with the actual state.

While this is less a problem for short files, with longer files, the AI may output a diff against their desynchronized view of the file, which fails to apply.

To reproduce

1. Create a new C source file with an empty main function:

#include <stdio.h>
int main(int argc, char **argv)
{
}

2. Ask the AI to write Hello World in the current file.

3. After an edit is suggested, ask the AI to add the functionality to print out argv[0]. The edit will not be carried out, but the interface of Continue marks this edit as accepted.

Log output

[danyalahmed1995]

I can take a look at this and try to reproduce it locally in the VS Code extension.Even though the original report is on Windows, the behavior sounds like it may be related to pending edit / follow up message state handling rather than OS specific file behavior.If I can reproduce it, I’ll look for a small focused fix so Continue does not treat a pending edit as successfully applied unless the edit was actually accepted/applied.
I’ll keep any PR scoped to this desync case and link it back here.