What Transfers Automatically
The one-click import migrates your complete VS Code environment: all installed extensions (ESLint, Prettier, GitLens, language servers, debuggers, themes), custom keybindings, user settings (settings.json), workspace configurations, code snippets, and recent project history. Cursor reads your VS Code profile directory directly — no export step required on the VS Code side.
Extensions install from the same marketplace sources. If you use extension-specific settings (like ESLint configuration paths or Prettier formatting rules), those transfer inside your settings.json. Cursor extensions are fully compatible with the VS Code extension API, so every extension works without modification.
Running Both Editors Side by Side
Cursor installs as a completely separate application. It does not modify, replace, or interfere with your VS Code installation. You can run both editors simultaneously, open different projects in each, and maintain separate configurations if desired. Some developers keep VS Code for specific workflows (like Remote SSH with custom setups) while using Cursor for AI-assisted development.
If you decide Cursor is your primary editor, you can uninstall VS Code without affecting Cursor. Conversely, removing Cursor leaves VS Code untouched. The getting started guide covers additional migration scenarios including keybinding customization and Cursor Rules for project-specific AI configuration.
