VSCode Import command enables extensions disabled in Vscode

Support Bug Reports
1

Describe the Bug

When initially starting to use cursor, I accepted the “Import from Vscode” option. While this brought over most of my extensions, several extensions that were disabled in vscode were installed and enabled in cursor leading to a negative experience in terms of performance and bloat.

Furthermore, when running the @command:cursorai.action.importvscode command from the pallete, the same behaviour was observed where extensions disabled in vscode were enabled in cursor.

Steps to Reproduce

  • Install an extension in vscode
  • Disable the extension globally
  • Run Import VS Code Extensions and Settings command
  • Observe that the extension is installed and enabled in cursor

Expected Behavior

While the extension should be installed, it should retain its enabled/disabled state from vscode

Operating System

MacOS

Current Cursor Version (Menu → About Cursor → Copy)

Version: 1.2.4 (Universal)
VSCode Version: 1.99.3
Commit: a8e95743c5268be73767c46944a71f4465d05c90
Date: 2025-07-10T16:55:16.443Z
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

Additional Information

The reason for globally disabling extensions is to enable them on a workspace basis as some significantly affect editor performance. Other times, they are language specific extensions and they are relevant to a select number of workspaces.

Does this stop you from using Cursor

No - Cursor works, but with this issue

2

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