I don’t have a cursor menu. I only see the new agents window. The VS code stuff is gone. Also about, cli, I’m executing the AppImage like this:
/opt/cursor/cursor.AppImage --appimage-extract-and-run --no-sandbox
This is the sha1 of the AppImage 7bb67bf97b77cb4ede1e8ec37ef295612b17fcb8
Hey, thanks for the detailed report with a screenshot and steps, it really helps.
I can see the new Agents Window with a ready-made plan and a Review button. This looks like a regression of a previously fixed bug in Plan Mode. The plan code gets read from disk during Build, skipping the in-memory edits in the editor, and then the agent overwrites the plan file. That’s why Ctrl+S doesn’t help. The editor model syncs with a file that has already been overwritten.
I’ve reported this internally as a regression in Glass UI and linked your thread. No ETA for a fix yet. Once there’s an update, I’ll post it here.
For now the workaround is limited. You can copy your plan additions into a follow-up message after Build like “also add X to step 2” so the agent takes them into account explicitly. It’s less clean, but it won’t get lost.
If you can find your Cursor version, even roughly like the install date or the last AppImage update date, please send it over. It’ll help narrow down which build this started in.
timestamp of AppImage is March 12, which by how fast things go today, is extremely old. I have downloaded latest AppImage and tomorrow will check if it fixed or not.
Can reproduce with the latest cursor (3.3.30 commit 3dc559280…)
One more detail I just noticed. If I don’t save the plan to workplace, I see the rollback visually. If I save the plan to workplace, agent also ignores changes, but I don’t get the rollback to the plan. So if changes are minor, it’s less obvious that they have been ignored.
Thanks for the update on the version and the extra detail about save to workspace, that’s a helpful nuance. Sounds like the symptom splits in two: without saving to workspace you see a visual rollback, with saving the agent still ignores the edits but there’s no rollback, so it’s easy to miss if the changes are small.
We’re tracking the bug, but there’s no fix ETA yet. If anything changes, we’ll update this thread.
For now the workaround is the same: resend important edits as a follow-up message after Build, so the agent picks them up clearly.
