Missing warning when switching back to earlier Composer

Bug Report
1

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, pleae check this box.
on

Describe the Bug

MINOR: Missing “not accepted” warning when switching back to earlier Composer session when there are un-accepted changes

Steps to Reproduce

  • Create a Composer session, do some things
  • Create another Composer session (e.g. when “Apply” hangs and won’t Cancel and the session becomes unusable… ahem)
  • Do some work in the second Composer session, maybe throw in a git commit or two, but leave the last change un-accepted in the Composer UI
  • Decide to check something in an earlier Composer session, switch back to it
  • Wonder why your most recent changes have vanished and git says your recently edited file is now empty

Expected Behaviour

There’s a helpful WARNING when you go to create a new Composer that this will mess up un-accepted changes. This warning should probably also happen when switching to a different pre-existing Composer too – either that or make it not clobber things on switch.

Operating System

MacOS

Current Cursor Version (Menu → Abount Cursor → Copy)

Version: 0.43.6
VSCode Version: 1.93.1
Commit: a846435528b4b760494a836f96f0739889253530
Date: 2024-12-06T05:11:55.168Z
Electron: 30.5.1
Chromium: 124.0.6367.243
Node.js: 20.16.0
V8: 12.4.254.20-electron.0
OS: Darwin x64 23.6.0

Additional Infomation

Does this stop you from using Cursor

No - Cursor works, but with this issue

1 Like