-
Notifications
You must be signed in to change notification settings - Fork 2.7k
Description
App Version
3.11.8
API Provider
OpenRouter
Model Used
N/A
Actual vs. Expected Behavior
When a user deletes a message from the conversation history by clicking the delete button, there is a chance that data loss will occur, preventing the conversation from continuing. Specifically, when the user clicks the delete button on a message and it disappears, it can sometimes cause the entire conversation to become stuck, and any subsequent messages will fail to trigger an API request, meaning the AI will not respond.
While the conversation history remains viewable, new messages cannot be sent. Upon investigation, it was found that the corresponding api_conversation_history.json file has been cleared, containing only an empty array ([]).
I have encountered this bug twice already.
Detailed Steps to Reproduce
The issue typically arises when deleting the same message twice or more in sequence. For example:
- The user deletes message A and returns to the position of message A;
- The user sends a new message B, cancels the API request, then deletes B;
- On sending a new message again, no API request is triggered, and the AI does not respond. The VSCode extension logs show no errors during this process.
Relevant API Request Output
Additional Context
No response
Metadata
Metadata
Assignees
Labels
Type
Projects
Status