Hi, thanks for reporting an issue with Cursor.
Before you report this, we’d appreciate if you can search this forum to see if this issue has already been reported.
If you have done so, please check this box.
on
Describe the Bug
When clicking restore on an earlier state while a generation is on-going, the remaining part of the messages are grayed out but the generation and applying of changes continues in the background leading to a state where the restored state is modified without the user’s consent.
Steps to Reproduce
Let composer in agent mode start working on a complex problem, let it create two code blocks and let it keep on talking,
click restore on one of the intermediate solutions.
Expected Behavior
When restore is clicked, the rest of the conversation is grayed out and the files are restored to their state at the checkpoint, the agent either completely stops generating their on-going response or at least fully refrains from applying changes to files.
Operating System
MacOS
Current Cursor Version (Menu → About Cursor → Copy)
Version: 0.44.9
VSCode Version: 1.93.1
Commit: 316e524257c2ea23b755332b0a72c50cf23e1b00
Date: 2024-12-26T21:58:59.149Z
Electron: 30.5.1
Chromium: 124.0.6367.243
Node.js: 20.16.0
V8: 12.4.254.20-electron.0
OS: Darwin arm64 24.1.0
Additional Information
Somewhat related - there is no cancel generation button when the composer is writing code? When I see it going off the rails, I want it to stop, but it is impossible to interrupt it while it is generating code and then it immediately applies it and starts generating more code – hence the reliance on the restore feature working.
Does this stop you from using Cursor
Sometimes - I can sometimes use Cursor