Migrating from Cursor to Craaft: A Step-by-Step Guide
Love the AI features of Cursor but miss your favorite IDE? Here's how to get the best of both worlds with Craaft.
Kevin M.
Founder
Why Switch?
Cursor is a great product. The AI integration is solid, the UX is polished. So why would you switch to Craaft?
Common reasons we hear:
The Migration Steps
Step 1: Install Craaft
The whole process takes about 2 minutes.
Step 2: Set Up Your API Key
Craaft needs access to Claude (or Codex). You'll need:
Step 3: Open Your Favorite IDE
This is the best part: just open your IDE. Zed, Neovim, VS Code (original), WebStorm, whatever you prefer.
Craaft runs alongside your IDE, not instead of it.
Step 4: Learn the Workflow
The Craaft workflow is slightly different from Cursor:
The mental model: Craaft is a powerful chat panel that understands your codebase. Changes appear in your IDE through the CLI.
Step 5: Customize Your Setup
Craaft settings you'll want to configure:
Features You'll Gain
Things Craaft has that Cursor doesn't:
✅ Prompt Queue - Stack prompts while AI works
✅ Multi-provider - Switch between Claude and Codex
✅ 100% Local - Code never leaves your machine
✅ IDE Freedom - Use literally any editor
✅ File Browser - Notion-like file navigation
Features You'll Miss (For Now)
Being honest, Cursor has some things we don't (yet):
❌ Inline editing - Cursor's Cmd+K is slick
❌ Autocompletion - Native integration with Copilot-style completion
❌ Integrated terminal - We use your system terminal
We're working on ways to close these gaps while maintaining our local-first architecture.
Tips for a Smooth Transition
The Bottom Line
If you value IDE freedom and privacy, the switch is worth it. If Cursor's inline editing is essential to your workflow, you might want to wait for our upcoming features.
Either way, the 14-day trial is free. Try it alongside Cursor and see which fits your workflow better.