Strange and confusing UI elements in agent-edited file list

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

In the bottom of the chat window, a list of files edited by the agent builds up over time. They have secret, hidden buttons that only show when you mouseover them but sometimes, for no apparent reason it has different options.

Some of these files have reject/accept changes, indicating that I can accept the agent’s edit (which always seemed strange to me since they are always “accepted” and in the code by default) or reject/undo them. This has nothing to do with git source control.
Other files have only ONE button - stage file. This is a source control action which is both inexplicable and seems wildly out of place since nothing else in this section of the UI is related to source control in any way.

Steps to Reproduce

Have it make files, I guess? I don’t know what the difference is between the files so it’s impossible to say.

Expected Behavior

I expect consistent and understandable UI behavior.

Screenshots / Screen Recordings

Operating System

Windows 10/11

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.0.77 (user setup)
VSCode Version: 1.99.3
Commit: ba90f2f88e4911312761abab9492c42442117cf0
Date: 2025-11-13T23:10:43.113Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Windows_NT x64 10.0.26100

For AI issues: which model did you use?

Not relevant but Composer 1

For AI issues: add Request ID with privacy disabled

7416e7dc-ca27-4c84-8123-fc2512eb525a

Additional Information

Again, your forum/bug report tool design is fantastically confidence-inspiring. You can attach only one file despite the header being pluralized as “ScreenshotS/ Screen RecordingS”. The file open dialog allows only a single selection, and if we click the button again to upload another file, the original upload is overwritten. Editing the post after posting lets us add more screenshots.

Does this stop you from using Cursor

No - Cursor works, but with this issue

Hey, thanks for the report. You’re right, this is confusing UI behavior.

Mixing Composer-specific actions (accept/reject changes) with git operations (“stage file”) in the same file list is inconsistent and shouldn’t vary unpredictably between files.

To help the team better understand the pattern, could you share:

  • For the files that show “stage file”, are they newly created or existing files?
  • What’s the git status of these files (untracked, modified, staged)?

Thanks again for flagging this!

As I said “I don’t know what the difference is between the files so it’s impossible to say.”.

My only guess could be that possibly the difference is for existing files vs new files the agent just created.