Import from VS Code
Bring your extensions, settings, and keybindings from VS Code into EngineForge. Everything transfers in one step with no manual exporting or file copying required.
What gets imported
EngineForge can import three categories from an existing VS Code installation. Each one is optional, so you choose what to bring over.
| Category | What transfers |
|---|---|
| Extensions | All extensions installed in VS Code are looked up in the marketplace and installed into EngineForge. Extensions that aren’t available are listed in the results summary. |
| Settings | Your settings.json is merged into EngineForge’s settings. Existing EngineForge settings are preserved and only new keys are added. |
| Keybindings | Your keybindings.json is copied over. If EngineForge already has custom keybindings, the import is skipped to avoid overwriting your work. |
Automatic import on first launch
The first time you open EngineForge, it scans your system for VS Code installations. If one is found, a dialog appears asking what you’d like to import.
- EngineForge detects VS Code (Stable, Insiders, or both)
- If multiple installations are found, you pick which one to import from
- A dialog shows checkboxes for Extensions, Settings, and Keybindings, all checked by default
- Click Import to start, or Skip to dismiss
This prompt only appears once. If you skip it, you can always run the import manually later.
Manual import
You can trigger the import at any time from two places:
From Settings
- Open EngineForge Settings (gear icon in the agent header, or
Cmd+,/Ctrl+,) - Go to the General tab
- Click Import next to “Import from VS Code”
From the Command Palette
- Open the Command Palette (
Cmd+Shift+P/Ctrl+Shift+P) - Search for Import from VS Code
- Select it to open the import dialog
Supported installations
EngineForge automatically detects these VS Code variants based on your operating system:
| Platform | Detected installations |
|---|---|
| macOS | VS Code (Stable) and VS Code Insiders |
| Windows | VS Code (Stable) and VS Code Insiders |
| Linux | VS Code (Stable) and VS Code Insiders |
How it works
- Extension scan: EngineForge reads the VS Code extensions directory and collects every installed extension ID
- Marketplace lookup: Each extension is looked up in the marketplace. Extensions that are available are queued for installation
- Installation: Extensions are installed in parallel. A progress indicator shows the current status
- Settings merge: Your VS Code
settings.jsonis parsed and merged into EngineForge’s settings file. Existing keys are not overwritten - Keybindings copy: Your
keybindings.jsonis copied if EngineForge doesn’t already have custom keybindings - Results: A toast notification appears showing how many extensions were installed, how many settings were imported, and whether keybindings were transferred. Any extensions not available in the marketplace are listed separately
Good to know
- The import is additive. It never removes or overwrites existing EngineForge configuration
- You can run the import multiple times. If you install new extensions in VS Code later, re-running the import will pick them up
- Extensions that are exclusive to VS Code (not published to the open marketplace) will be listed as unavailable in the results
- EngineForge-specific settings (agent, bridge, graph) are never affected by the import
- No data is sent to any server. The import reads directly from your local VS Code installation directory