Cursor ditches VS Code, but not everyone is happy...
What it is
Cursor started as a VS Code fork with AI bolted on. Version 3 throws that out and replaces it with a custom-built editor. Think of it as Cursor saying 'we've learned enough—time to build from scratch.' The new architecture is designed around AI-first workflows instead of retrofitting AI into an editor built for humans typing code line-by-line.
Why it matters
If you're deep in Cursor, this matters because your extensions might break and muscle memory might friction. But the bet here is speed—AI code generation is bottlenecked by editor responsiveness, not model latency. If Cursor's custom editor is genuinely faster at handling AI edits, diffs, and multi-file changes, it's worth the migration pain. If not, you're stuck in a proprietary editor that's behind VS Code's ecosystem.
Key details
- •Cursor 3 uses a proprietary editor codebase, not a VS Code fork
- •Company claims performance improvements for AI-native workflows like multi-file edits and large diffs
- •VS Code extension compatibility is uncertain—some extensions may not work or require rewrites
- •User backlash centers on losing the VS Code ecosystem and being locked into Cursor's roadmap
- •This is the first major AI editor to fully abandon VS Code's foundation
Worth watching
Video data provided by YouTube. Videos link to youtube.com.