Approve file edits

Bug Reports
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Cursor is now asking me to approve file edits inline in the agent chat, which it never used to do. And much of the time it is not displaying the approval button in the Agent chat window.

Steps to Reproduce

Request to approve file edit seems to be happening with all file edits. The missing approval button is seemingly happening more frequently with Composer selected.

Expected Behavior

I expect the Agent to make the file edits and I review them in the IDE.

Operating System

Windows 10/11

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.1.44 (user setup)
VSCode Version: 1.105.1
Commit: f6a8593b2b7c61c2063c79d5a8fcd248c9db4580
Date: 2025-12-01T22:52:09.315Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Windows_NT arm64 10.0.26200

For AI issues: which model did you use?

Auto, Composer

For AI issues: add Request ID with privacy disabled

bf98f455-5bd9-44b0-8800-a119110747b9

Does this stop you from using Cursor

Sometimes - I can sometimes use Cursor

1 Like
2

Hey, thanks for the report. I see that in v2.1.44, the agent asks to confirm edits inline, but the confirmation button sometimes doesn’t appear (more often with Composer).

It seems to overlap with worktree/protection bugs:

Temporary workaround:

  • Settings → Agents → Auto-Run Mode → Run Everything
  • Temporarily disable External-File Protection and Dotfile Protection
  • Ask the model to use relative paths when editing

Could you please share:

  • A screenshot/video of the agent chat when the confirmation button is missing
  • Errors from Help > Toggle Developer Tools > Console at that moment
  • Logs from View > Output > Cursor and Agents for the same session
  • Output of commands:
  • In the repo root: git worktree list git status
  • In the active worktree: git status
  • Indicate if it reproduces without Composer (e.g., with Auto/Chat)

Please provide this data and I’ll pass it on to the team.

1 Like
3

Here is a screenshot of it waiting for approval with no button present. This is with Auto Agent, so the Composer part mentioned is a red herring. This is also after having enabled “Run Everything” and restarting Cursor and trying to do this via a new Agent chat.

image
image601Ă—335 23.9 KB

image
image567Ă—544 20.2 KB

image
image681Ă—101 2.52 KB

1 Like
4

also the Keep changes button is broken with notebooks. It doesnt do anything.
Version: 2.1.46
VSCode Version: 1.105.1
Commit: ab326d0767c02fb9847b342c43ea58275c4b1680
Date: 2025-12-02T03:59:29.283Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Linux x64 6.17.8-300.fc43.x86_64

5

Thanks for the details and screenshots.

This matches a known issue with edit confirmations (including near worktrees).

For now, check:

  • Temporarily disable External-File Protection and Dotfile Protection
  • Ask the model to use relative paths for edits

For the case without the button, please send:

  • Request ID from the message’s context menu (where it asks for confirmation), when there’s no button
  • Errors from Help > Toggle Developer Tools > Console at that moment
  • Are symlinks/mounted disks being used?

@VihangaFTW For notebooks (“Keep changes” does nothing): this seems like a known topic There is no "undo" feature for Jupyter notebook inside the chat. Only "Keep All"
You can attach:

  • Minimal .ipynb and exact steps
  • Request ID at the moment of clicking the button
  • Console errors (Help > Toggle Developer Tools > Console)

As soon as I get this data, I’ll pass it to the team.

6

I think this is related to the terminal that hasn’t worked for 3 releases also - the terminal won’t work unless you tell the agent to populate the “working directory” parameter - so clearly its unaware of its working directory, thus it thinks its editing files outside of it, which requires approval.

I can’t even fathom how they’ve broken agents for 3 releases and not picked up on this.

7

I got the same issue out of the sudden when updated to latest version.