extensions.autoUpdate setting not available via MDM

Support Help
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Hi,

I want to configure and deploy a cursor config via our MDM for MacOS laptops. I would like to configure the extensions.autoUpdate setting (which is available in VSCode) but it is missing in the latest Cursor version.
As far as I understand, the setting “UpdateMode” is only scope to the Cursor application and not the extensions.

Did I miss anything? Could you add it back to the Cursor config? so it can be managed via MDM

Thank you!

Steps to Reproduce

Create a cursor config file (.mobileconfig file) with the key:
“”"
ExtensionsAutoUpdate
off
“”"

This works on VSCode but not for Cursor.

Expected Behavior

Prevent Cursor extensions to be automatically updated

Operating System

MacOS

Version Information

Version: 3.8.23 (Universal)
VS Code Extension API: 1.105.1
Commit: 7cf19b7482706625cdb70db3211b7dd035b7aa30
Date: 2026-06-23T14:57:42.334Z
Layout: editor
Build Type: Stable
Release Track: Default
Electron: 40.10.3
Chromium: 144.0.7559.236
Node.js: 24.15.0
V8: 14.4.258.32-electron.0
xterm.js: 6.1.0-beta.256
OS: Darwin arm64 24.6.0

Does this stop you from using Cursor

No - Cursor works, but with this issue

5

Hey, thanks for the detailed report. You understood it correctly. UpdateMode update.mode only applies to the Cursor app updater, it doesn’t apply to extensions.

About extensions.autoUpdate: the setting exists in Cursor and works locally, but unlike VS Code it isn’t registered as an MDM policy yet, so there’s no ExtensionsAutoUpdate key in Cursor .mobileconfig profiles. Right now the profile only supports AllowedExtensions, AllowedTeamId, ExtensionGalleryServiceUrl, and UpdateMode.

Workaround: deploy a managed settings.json via MDM with:

{
  "extensions.autoUpdate": false,
  "extensions.autoCheckUpdates": false
}

This will stop extension auto-updates on machines. The downside is that unlike a real MDM policy, this settings.json is still editable by the user, so it doesn’t provide strict enforcement.

Expanding the MDM policy set including ExtensionsAutoUpdate is already tracked as a request here: MacOS managed settings. I’d recommend adding your use case there so it’s captured in one place. I’m moving this thread to Feature Requests.

6

Sure! Thanks for the quick response.