What it does
Because Cursor is built on VS Code, the extension model is the same one you know: an extensions pane, a search box, and per-workspace or global installs. Language servers, formatters, themes, debuggers and linters generally work without modification.
The exception is the small set of extensions Microsoft licenses only for its own builds of VS Code. Those are unavailable in any fork, Cursor included, and the usual answer is an open equivalent from the marketplace Cursor uses.
If you are moving from VS Code, Cursor offers to import your existing extensions, settings and keybindings on first run, which is usually the fastest way to arrive at a familiar editor.
Using it
- Import from VS Code. On first launch, accept the prompt to bring over extensions, settings and keybindings. It can also be triggered later from the settings.
- Install individually. Open the extensions pane, search, install. Workspace recommendations in .vscode/extensions.json are honoured.
- Find replacements where needed. If a Microsoft-licensed extension will not install, search for the open alternative, which usually exists for the common cases.
Checked against Extensions in the Cursor help centre on 25 September 2026.