CursorGetting startedLevel 1: Basic prompts

How Do You Move From VS Code to Cursor?

Open Cursor Settings with Cmd+Shift+J (Ctrl+Shift+J on Windows and Linux), go to General > Account, and click Import under VS Code Import. That brings over your extensions, themes, settings and keybindings. Most of it will feel the same, but extensions come from a different store, so check the ones you depend on.

Prompt to copy
Cursor Settings (Cmd+Shift+J or Ctrl+Shift+J) > General > Account > VS Code Import > Import

For more control, in VS Code run this from the Command Palette, then export the profile:
Preferences: Open Profiles (UI)

In Cursor, run the same command and choose Import Profile from the dropdown next to New Profile.
Do
  • Check each extension's publisher
  • List missing extensions before uninstalling VS Code
  • Remap Cmd+K chords if you rely on them
Don't
  • Match an extension by ID alone
  • Expect every Marketplace extension on Open VSX
  • Expect rules to come in a profile export
Rule of thumb, based on Cursor's migration and extension docs.

Try it now

  1. 1Press Cmd+Shift+J (Ctrl+Shift+J on Windows and Linux) to open **Cursor Settings, then go to General > Account**.
  2. 2Click Import under VS Code Import, and wait for it to finish.
  3. 3Press Cmd+Shift+X (Ctrl+Shift+X) to open the Extensions panel and look for the three extensions you use most. It worked if your theme and keybindings match VS Code and those extensions are installed.

Use it when

You're moving from VS Code and want your editor to feel the same on day one. Also use the manual profile route when you're moving between machines or want to bring over only one profile.

Skip it when

If your VS Code setup is bloated, you may prefer to start clean and add extensions as you miss them. You also don't have to switch outright: Cursor's help says the two run as separate applications and can both open the same project.

Why it works

Cursor is built on the VS Code codebase, so settings and themes transfer directly. Extensions are the exception. Cursor's docs say it uses the Open VSX registry, not the Microsoft Marketplace, so not every extension is listed. Cursor routes search and downloads through its own proxy at marketplace.cursorapi.com, which runs automated malware and supply-chain checks before an extension is offered. It also publishes first-party Anysphere replacements for some widely used extensions that aren't on Open VSX.

Example

Say your team relies on a language server, a formatter and a Microsoft extension for remote work. After the import, the theme and formatter settings are in place, but you open the Extensions panel to check each one's publisher, since a missing Microsoft extension may not be on Open VSX. If an Anysphere replacement exists, that's the one Cursor offers. Note the names you can't find before you uninstall VS Code.

Going further

Treat extension IDs like dependencies. Cursor's extension docs warn that the same publisher.extension name can point to a different publisher or different code on Open VSX than on the Microsoft Marketplace, so check the publisher rather than the name alone. Your shortcuts also differ in one place worth learning early: the docs open the shortcuts editor with Cmd+R then Cmd+S (Ctrl+R then Ctrl+S), while VS Code's own default is Cmd+K Cmd+S. In Cursor, Cmd+K opens Agent.

Common mistakes

  • Assuming every Marketplace extension will appear. Cursor's docs say many popular ones are available, but not all, and some may work differently.
  • Installing an extension by matching its ID without checking who published that version on Open VSX.
  • Pressing Cmd+K to start a VS Code chord and having Agent open instead. Remap it under Keyboard Shortcuts if you rely on those chords.
  • Expecting user and team rules to come along in a profile export. Cursor's help says they aren't included, though signing in syncs account user rules.

Sources

Checked 6 November 2026. Products change often, so confirm details with the vendor.

Related

Beyond the course