File handling fragile when rejecting new file creation

Bug Reports
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

File handling is fragile when rejecting changes that create new files.

Steps to Reproduce

  • Use Composer to generate code that will be placed in a new file
  • Reject the change
  • Try again causing code to go to the same file
  • Note the absence of the file on the filesystem even though the IDE thinks the diff has been applied

Expected Behaviour

The new file should become accessible in the project tree and on the filesystem

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

It’s possible to work around it by manually creating the missing file, which will be empty, and then using copy+paste to take the intended file contents and insert them in there. It will then work normally after doing that.

Does this stop you from using Cursor

No - Cursor works, but with this issue

1 Like
2

Also just a suggestion - from a UX perspective, on the bug form:

Does this stop you from using Cursor

could perhaps benefit from being re-worded. My brain halted (luckily didn’t catch fire) from the positive/negative mismatch when reading the options (yes this is not not good, vs no this is not bad).

Maybe “Are you still able to use Cursor”?

Yes - good
No - bad

3

Hey, thanks for sharing this.

1 Like