Basics
Migrating to Cursor from VS Code
Cursor has a one-click VS Code Import. Open Cursor Settings (Cmd/Ctrl + Shift + J), go to General → Account and click Import under VS Code Import to bring over your extensions, themes, settings and keybindings. Cursor installs extensions from the Open VSX registry, not the VS Code Marketplace. It is a separate app, so you can keep VS Code installed.

On this page
How do I import my VS Code settings?
The import lives in Cursor Settings, so you can run it whenever you like, including after you have used Cursor for a while. It takes three steps.
- 1Open Cursor Settings: Mac press
Cmd+Shift+J; Windows/Linux pressCtrl+Shift+J. - 2Go to General → Account.
- 3Under VS Code Import, click the Import button.
That one click brings over your extensions, themes, settings and keybindings. Extensions and keybindings are the two that need checking afterwards, which is why most of this page is about them.
Cursor's help page says what the import brings over, but not what it does with settings you have already changed in Cursor. If you have set up a theme and a font and then click Import, the page doesn't say whether your choices survive or get replaced. Run the import on a fresh install, before you customize anything, and the question doesn't come up.
If you have used Cursor for months, run the import anyway. If it does overwrite something, putting it back takes an evening, and your whole old keymap arrives in one click.
This is covered hands-on in Cursor First Hour — 4 short Units, free to read.
Rather do it than read about it? Run 11 interactive Cursor walkthroughs in a simulated editor. Free, no account needed.
Does Cursor support my VS Code extensions?
Many of them. Cursor installs extensions from the Open VSX registry, not the VS Code Marketplace. Most popular extensions are on Open VSX, but some may not be listed, and some that are listed may not work exactly the same way. Our install guide covers how to check your own list.
The import can also bring over what you don't want. One click copies all your extensions, including any other assistant that was completing your code in VS Code. Cursor's troubleshooting page says extensions that ship their own AI completions or grab keyboard shortcuts can conflict with Cursor, and it names other AI coding assistants as the most common source. If you run any of those in VS Code today, decide what to do with them before you click Import.
If Tab goes quiet on your first morning in Cursor, or a shortcut does nothing, start in the Extensions panel (Cmd/Ctrl + Shift + X) and disable the other assistant before you change anything else. If the panel won't open, you may be in the Agents WindowCursor's surface listing your agent runs; open a run to read its diff and search transcripts from the command palette. Press Enter for the full definition.: run Open IDE from the command palette first. For a conflict you can't place, the elimination routine in our troubleshooting guide finds it faster than reading extension names.
Cursor's help page says what the import brings over. It doesn't say what happens to an extension that has no Open VSX equivalent, so open the Extensions panel afterwards and confirm that the two or three you depend on are installed and enabled.
Do my keyboard shortcuts work?
Mostly, yes. Cursor ships VS Code's default shortcuts, so the keys you already press keep doing what they did, and your custom keybindings come across with the import.
Cursor's AI shortcuts sit on top of those defaults. Cmd/Ctrl + I, L or K opens the AI side panel, and with code selected, Cmd/Ctrl + L or K opens Agent with those lines in the input. Cmd/Ctrl + . opens the mode menu, Shift + Tab rotates through the agent modes, and Cmd/Ctrl + / loops between models.
The key that catches VS Code users is Cmd + K. In VS Code it starts two-step chords, but Cursor uses it for its AI features, so those chords moved to a different leader. Older Cursor guides describe Cmd + K as inline edit, which Cursor has replaced with sending the selection to Agent. Our keybindings.json guide has the chord mapping.
When a chord stops working, don't paste your old keybindings.json across. Imported entries have turned up with when fields reading (arbitrary function), a placeholder left where a condition couldn't be carried over, and those bindings never fire. Delete them and rebind through the Keyboard Shortcuts screen: Cmd + R then Cmd + S on Mac, Ctrl + R then Ctrl + S on Windows and Linux.
Should I use the one-click import or export a profile?
Use the one-click import unless you have a specific reason not to. Exporting a profile from VS Code and importing it by hand is the route Cursor points to when you want more control over what moves, and its VS Code migration guide has the steps.
Cursor's pages give two reasons for the manual route, moving between machines and wanting more control, without saying what that control buys you. In our view, it pays off when you already know something in your VS Code setup shouldn't follow you: a dead extension you never uninstalled, or the second AI assistant from the section above. Without a reason that specific, use the one-click import.
On your own machine, this choice takes a minute. Across a team of forty, the extension question gets asked forty times instead of once, and the people who hit it after they switch are the most likely to give up on the move. So do the lookup once, before you set a rollout date. Write the answer down in two columns: what your build and lint steps depend on, and what to use where Open VSX has nothing.
Can I run both Cursor and VS Code?
Yes. Cursor and VS Code install as separate applications, and both can work on the same projects, so nothing forces a decision on day one.
Running both for months has a cost. The import is an action you run, and Cursor's help page doesn't describe it as an ongoing sync, so don't treat it as one. If you keep editing settings in both editors, they drift apart, and a formatter ends up behaving differently on the same file in two windows. You then lose an afternoon comparing config.
There is nothing to roll back in this migration, so the risk is a switch that never finishes: six months with both editors open and half your configuration in each. Move one real project across completely and stop opening it in VS Code. That tends to settle the switch within a week.
Frequently asked questions
What exactly does the VS Code Import bring over?
Your extensions, themes, settings and keybindings, in one click from Cursor Settings → General → Account → VS Code Import.
Why isn't one of my VS Code extensions available in Cursor?
Cursor installs extensions from the Open VSX registry rather than the VS Code Marketplace. Many popular extensions are on Open VSX, but not all of them are listed, and some behave differently.
Can I import only part of my VS Code setup?
Yes. For more control than the one-click import gives you, export a profile from VS Code and import it manually. Cursor's VS Code migration guide covers the steps.
Tab or a shortcut stopped working right after I imported. What now?
Extensions that ship their own AI completions or grab keyboard shortcuts are the usual cause, and other AI coding assistants are the most common one. Open the Extensions panel (⌘⇧X on Mac, Ctrl⇧X on Windows and Linux) and disable the other assistant. If that doesn't find it, run Disable All Installed Extensions from the command palette and re-enable them one at a time until the conflict comes back.
Do my two-step Cmd+K chords still work in Cursor?
Not as they were. Cursor uses ⌘K for its AI side panel, so chords that started with ⌘K moved to a different leader. Some imported entries also arrive with a when field reading (arbitrary function) and never fire. Delete those and rebind through the Keyboard Shortcuts screen: ⌘R then ⌘S on Mac, CtrlR then CtrlS on Windows and Linux.
Sources & last verified
- Cursor - Migrate from VS Code
- Cursor - Extensions
- Cursor - Extensions troubleshooting
- Cursor - Keyboard shortcuts
- Cursor - VS Code migration guide
- Cursor Help: Agent mode
Cursor ships frequently. Last updated October 28, 2026.