Flintr is in development.

flintr
Back the launch

Switching from Cursor

Switch from Cursor in under a minute.

Flintr reads your Cursor profile and moves everything across: extensions, settings, rules, MCP servers and chat history. Same plans, same muscle memory, different owner.

Back the launch
$ flintr import --from cursor

Flintr is in development. The importer ships with the private beta, which backers from €25 get first.

How to switch

4 steps, about two minutes.

  1. 1

    Download Flintr

    Install it next to Cursor. Nothing is changed or removed from your Cursor install.

  2. 2

    Run the import

    Choose "Import from Cursor" on first launch, or run flintr import --from cursor in any terminal. It takes about 40 seconds for a typical setup.

  3. 3

    Pick the plan you already had

    Pro, Pro+ and Ultra work the way you're used to, except on-demand usage is billed at the provider's list price.

  4. 4

    Cancel Cursor when you're ready

    Keep both for a while if you like. When you're happy, cancel your Cursor subscription from its account settings.

✔ Found Cursor profile at ~/.cursor
✔ Imported 42 extensions and 3 themes
✔ Imported keybindings and settings.json
✔ Converted 7 project rules → .flintr/rules
✔ Connected 3 MCP servers (github, linear, postgres)
✔ Migrated 1,284 chats to local history
Settings sync: on · Privacy mode: on

What comes across

Everything you set up, carried over.

The import only reads your Cursor profile. Nothing is changed or deleted, so you can run both editors side by side.

  • Extensions, themes and keybindings
  • settings.json and workspace settings
  • Project rules (.cursor/rules → .flintr/rules)
  • Legacy .cursorrules files
  • MCP servers and their credentials
  • Chat history and saved prompts
  • Your own API keys, if you used them

What's different

The parts you'll notice.

Usage is shown in dollars

No credits or request multipliers. Every request shows what it cost, at the provider's list price.

Hard caps are really hard

Set a monthly cap and choose what happens when you reach it: fall back to fast models or pause premium requests.

Every model, no favourites

Claude, GPT, Gemini, open-weight models and more, with no house model ranked above the rest.

See the full Flintr vs Cursor comparison

FAQ

Switching from Cursor, answered.

Will my Cursor rules work unchanged?

Yes. Project rules in .cursor/rules are copied to .flintr/rules with the same front matter, and legacy .cursorrules files are converted automatically. Your original files are left in place.

Do I lose my chat history?

No. The import copies your chat history and saved prompts into local history, so you can search and continue old conversations.

Do my MCP servers come across?

Yes, including their configuration and credentials. They connect automatically after the import, and the summary lists each one so you can check.

Do the keyboard shortcuts stay the same?

Yes. Tab to accept, Cmd/Ctrl+K for inline edits and Cmd/Ctrl+L for chat all work the same, and any custom keybindings are imported.

Can I keep using Cursor at the same time?

Yes. The import only reads your Cursor profile, so both editors keep working side by side. You can re-run the import at any time to pick up changes.

Switching from somewhere else? VS Code or Windsurf.

Be among the first to move in.

Back the launch from €25 to switch during the private beta, before downloads open for everyone.

Back the launch
See planned pricing

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