Get started
Migrating from Cursor
Import your editor settings and colour themes from an existing Cursor installation.
Run the import
In the desktop app, open Settings and find "Import from another editor" on the General page. Choose Cursor. Goatfied reads Cursor's configuration on this machine, applies what it can, and reports what it took and what it left behind.
Cursor is read and not written to. Both editors can stay installed and open the same project; they keep separate configuration and separate state.
What comes across
Editor settings, where there is an equivalent here: font, line height, ligatures, tab width, word wrap, line numbers, 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.
Colour themes from your installed theme extensions, with the one named in your settings selected if we found it.
If you already keep project rules files, those are picked up separately as rules — that happens per project and is not part of this import.
What does not, and why
Extensions do not run here. There is no extension host, so nothing an extension contains can execute. Cursor's extensions are read only far enough to find colour themes in them. Formatting and language tooling are built in rather than installed.
Custom keybindings do not transfer. Shortcuts are not yet remappable here, so a keybindings.json has nowhere to go. The import will tell you if it found one instead of quietly ignoring it.
Anything else you had set is listed back to you as not imported, so you can decide what to set again rather than finding out by surprise.
Where Cursor keeps these files
On macOS, ~/Library/Application Support/Cursor/User/; on Windows, %APPDATA%\Cursor\User\; on Linux, ~/.config/Cursor/User/. Extensions live in ~/.cursor/extensions.
Chat history and agent sessions
Conversations do not come across. They are stored in a private format that is specific to the editor that wrote them, and importing them would mean guessing at a structure nobody publishes. Start fresh — your codebase is the context that matters, and that is read here directly.