Cursor › Composer: Should Auto Accept Diffs defaulting to true in latest release

[Jon_Fenner]

Describe the Bug

I was confused to see that Cursor › Composer: Should Auto Accept Diffs defaulting to true in latest release (cursor.composer.shouldAutoAcceptDiffs) is defaulting to “true” now in the latest update. This is confusing to users like myself wondering where the “Keep All” button went. It should default to “false” or to the previous value the user has set.

Steps to Reproduce

• Install an older version of Cursor (1.2)
• Make a cursor code change request and note that “Keep All” shows up
• Upgrade to Version: 1.3.3 (Universal)
• Make a cursor code change request and note that it does not confirm the changes

Expected Behavior

Should by default NOT auto accept diffs

Operating System

MacOS

Current Cursor Version (Menu → About Cursor → Copy)

Version: 1.3.3 (Universal)
VSCode Version: 1.99.3
Commit: e589175333a2d938c3d944f9bf0993155e655e70
Date: 2025-07-26T19:15:12.946Z
Electron: 34.5.1
Chromium: 132.0.6834.210
Node.js: 20.19.0
V8: 13.2.152.41-electron.0
OS: Darwin arm64 24.5.0

Does this stop you from using Cursor

No - Cursor works, but with this issue

[condor (Condor (Tee))]

Hi @Jon_Fenner and thank you for the detailed bug report.

This is a setting in 1.2.4 (clean installation) and 1.3.3 that allows auto-accepting on commit only.

Both have that feature in Editor Settings and in Settings > Chat, which can be toggled as well.

[Jon_Fenner]

Understand it’s a setting, it’s just odd that all of a sudden it was enabled when I didn’t enable it. Causes confusion…