Cursor deleting experimental settings

Support Bug Reports
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

I believe the issue was reported here Settings.json keys like extensions.experimental.affinity are deleted on restart in September of 2025 but it still is happening on the latest version, any ETA on the fix?

Steps to Reproduce

Set experimental settings

“extensions.experimental.affinity”: {
“asvetliakov.vscode-neovim”: 1
}

Open settings.json in Cursor.
Add the snippet above under your settings.
Save and restart Cursor.
Observe that the extensions.experimental.affinity entry is gone.

Expected Behavior

Cursor should not silently delete unknown or experimental configuration keys from settings.json. Even if the key is unsupported, it should remain untouched instead of being stripped out on restart.

Operating System

Linux

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.3.23
VSCode Version: 1.105.1
Commit: 655ee705c6c7b6da1da481d0fdf13191d5e3e980
Date: 2026-01-06T04:26:58.029Z
Electron: 37.5.1
Chromium: 138.0.7204.251
Node.js: 22.19.0
V8: 13.8.258.32-electron.0
OS: Linux x64 6.18.2-2-cachyos

Does this stop you from using Cursor

No - Cursor works, but with this issue

2 Likes
2

Hey @rayzorben

I did a bit of digging, and I can confirm that this isn’t a general issue with experimental settings, it’s specific to extensions.experimental.affinity and only for VIM extensions vscodevim.vim and asvetliakov.vscode-neovim.

Any particular reason you want to change the affinity for these extensions? Cursor should already be handling extension isolation for you.

(FWIW I don’t enjoy “magic” either, just want to understand what impact this is having for you!)

3

This is why :stuck_out_tongue: I get prompted with this all of the time.

image
image425×247 27.2 KB

4

Ah, I understand. :slight_smile: Let me follow-up on this. We’ve been rolling out some changes with extension isolation.

1 Like
7

Glad its acknowledged, this notification has been driving me nuts lol - gonna downgrade Cursor until its resolved.

8

+1 here, the editor should not be stepping on explicitly set user config.

1 Like
9

This is still an issue. +1

10

Good news, all! This will get fixed in 2.4.