Flintr is in development.

flintr

How to switch from Cursor to Flintr without losing anything

A step-by-step guide to moving from Cursor to Flintr: extensions, settings, project rules, MCP servers and chat history, in about two minutes.

Guides5 min read

Before you start

This guide describes how switching works in the Flintr private beta and at launch.

You don't need to uninstall or export anything from Cursor first. Flintr reads your existing Cursor profile and copies what it needs. Nothing in your Cursor install is changed or deleted, which means you can try Flintr for a week, or a month, before deciding.

The whole process takes about two minutes on a typical setup. Most of that is downloading the installer.

Step 1: Install Flintr

Install Flintr for macOS, Windows or Linux and open it. Sign in with GitHub, Google or email.

Flintr is in development, so installers aren't public yet. Backers from €25 get into the private beta first, and downloads open for everyone with the public beta.

Step 2: Run the import

On first launch, choose Import from Cursor. If you skipped that screen, open any terminal and run:

$ flintr import --from cursor

You'll see each step as it happens, followed by a summary of everything that was imported. If anything couldn't be brought across, such as an extension that isn't published on Open VSX, the summary lists it so you can install an alternative.

What gets imported

From CursorIn Flintr
Extensions and themesInstalled from Open VSX
settings.json and keybindingsCopied as they are
.cursor/rules.flintr/rules, same front matter
.cursorrules (legacy)Converted to a rule in .flintr/rules
MCP serversConnected, with their credentials
Chat history and saved promptsLocal history, searchable
Your own API keysAdded per provider

Rules and MCP servers

Project rules are copied, not moved. Your original .cursor/rules files stay where they are, and the new copies in .flintr/rules keep the same front matter, so globs and descriptions behave the same way. If your team still uses Cursor, commit both folders for a while.

MCP servers are imported with their configuration and connect automatically. The import summary lists each server, so it's easy to check that the ones you rely on, such as GitHub or your database, are connected.

After the import: plan and spend cap

Pick the plan you had on Cursor. Pro, Pro+ and Ultra have the same names and the same prices. The difference is what happens after your included usage: requests are billed at the provider's list price and every request shows its cost. See which plan fits your usage.

Then set a hard spend cap in settings and choose what happens when you reach it: fall back to fast models, or pause premium requests.

Troubleshooting

  • An extension is missing. A few extensions are only published on Microsoft's marketplace. The summary suggests an Open VSX alternative where one exists.
  • You changed something in Cursor after importing. Run the import again. It skips anything that has already been imported.
  • Something else. Email hello@flintr.ai with the import summary and we'll help.

Frequently asked questions

Does the import change my Cursor installation?

No. It only reads your Cursor profile. You can keep using Cursor exactly as before.

How long does the import take?

Usually under a minute. Most of the time is spent installing extensions.

Can I import more than once?

Yes. Running it again picks up anything new and skips what has already been imported.

The Flintr team

Written by the people who build Flintr. Questions or corrections? Email hello@flintr.ai.

Your editor. Your models. Your bill.

Flintr is in development and funded by the people who'll use it. Back the launch from €5, or from €25 to get into the private beta.

Coming to macOS 12+ · Windows 10+ · Linux (deb, rpm, AppImage)