Rejecting a single edit rejects ALL edits

Bug Reports
1

Repro steps:

  1. Ask cursor agent to make some changes to a file. It does so, perhaps using multiple edit calls. (call it edit #1) No problem.
  2. Without hitting “approval all”, ask cursor agent to make another edit. (call it edit #2). it does so.
  3. Click the ‘reject’ button specifically only on the most recent edit (#2).

Expected result:

  • Edit #2 is rejected, and edit #1 remains.

Actual result:

  • ALL edits in this session are rejected.

Version: 0.47.8
VSCode Version: 1.96.2
Commit: 82ef0f61c01d079d1b7e5ab04d88499d5af500e0
Date: 2025-03-18T06:55:51.040Z
Electron: 32.2.6
Chromium: 128.0.6613.186
Node.js: 20.18.1
V8: 12.8.374.38-electron.0
OS: Darwin arm64 24.3.0

2 Likes
2

I agree, usually I approve all but occasionally I need to one-off nitpick reject minor changes in the mix. Seems the new flow is you have to approve all and then manually go back to edit what you caught, but that is nonintuitive.

3

I created an account just to +1 this. “Reject all” should only reject changes since the previous prompt. Or at least, please show a warning “this will reject ALL changes since the start of this chat”. Frustrating experience to have “reject all” really be “reject all and then some”.

1 Like
4

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.