Migrating from VS Code

Run the import

In the desktop app, open Settings and find "Import from another editor" on the General page. Choose Visual Studio Code. Goatfied looks for VS Code's configuration on this machine, applies what it can, and then tells you what it took and what it left.

Nothing about your VS Code installation changes. The files are read and closed. You can keep both editors installed and open the same project in either one — they do not share state and will not interfere with each other.

What comes across

Editor settings, where there is something here that means the same thing: font family and size, line height, ligatures, tab width, word wrap, line numbers, the minimap, sticky scroll, bracket pair colouring, indent guides, whitespace rendering, cursor and scroll animation, folding, linked editing, format on save, inline suggestions, breadcrumbs, and auto-save with its delay.

Colour themes, taken from the theme extensions you have installed. If your settings.json names a theme that we found, it is selected for you; otherwise the imported themes wait for you under Settings → Appearance. You can also import a theme by hand at any time from a .json file or a .vsix.

What does not, and why

Extensions do not run here. Goatfied has no extension host, so a VS Code extension has nothing to execute inside. The import reads your extensions, but only to find the themes among them, and it tells you how many it saw. Formatting and language tooling are built in rather than installed, so much of what people reach for extensions to do is already present.

Custom keybindings do not transfer, because shortcuts here are not yet remappable. There is nowhere to put a keybindings.json. If you have one, the import will say so rather than pretend otherwise. The default shortcuts follow the conventions you already know.

Settings that have no equivalent are listed back to you after the import. That list is the honest one — a setting we silently dropped would turn up a week later as an editor doing the wrong thing for no visible reason.

Where VS Code keeps these files

You do not need to find them yourself, but if you want to check what is there: on macOS, ~/Library/Application Support/Code/User/; on Windows, %APPDATA%\Code\User\; on Linux, ~/.config/Code/User/. Extensions live in ~/.vscode/extensions.

If the import finds nothing

It is looking in the locations above. A VS Code installed through a sandboxed package manager, or one using a non-default profile, may store its configuration elsewhere. In that case open your settings.json in VS Code, copy the values you care about, and set them under Settings → Appearance.