Coming from Cursor? Bring everything.

Moving over

1. Download Celiador for macOS or Linux and open it.
2. On first launch Celiador notices Cursor or VS Code on your machine and offers to import. Missed it? Run Celiador: Import Settings from Another Editor from the command palette.
3. Sign in, open a folder, and start an agent run.

What comes with you

• Settings — merged into yours. Anything you already set in Celiador wins.
• Keybindings and snippets — added, never overwriting what you have.
• Extensions — installed from Open VSX, the open extension registry. The import tells you by name which ones it could not find there.

What deliberately doesn’t

• Cursor’s own settings, Cursor-only extensions and Copilot. Celiador has its own agent built in; two AI layers in one editor fight each other.
• Your Cursor account, chat history and indexes. Those stay with Cursor. Celiador doesn’t build a server-side index of your code at all.

What’s different here

• Claude is the agent, by design. Not one option in a model menu that can change under you.
• Your agent runs on your machine, and your phone drives it. Start a run from the iPhone app on the repo your Mac has open, approve tool calls, answer questions, review the diff, commit and open the pull request.
• One pricing truth. The limits we enforce are published as numbers, live from the same service that meters you — see pricing.
• We never train on your code, and your code stays local — privacy, in plain words.

If you’re leaving because of billing

Most developers who switch tools don’t leave over features. They leave when a plan changes under them, a limit appears that wasn’t there before, or a model they relied on disappears from the menu. We can’t promise we’ll never change a price. We do promise how we’ll do it — dated notice, grandfathering with an end date, and cancelling as easily as you joined. That’s written down in our conduct pledge, and you can hold us to it.