Tool Update2h ago
Cursor ditches VS Code, but not everyone is happy...
🧠
Visual pending
What it is
Cursor started as a VS Code fork with AI features bolted on. Version 3 replaces that foundation with a custom-built editor. Picture tearing down a renovated house to build new from the ground up — you get exactly what you want, but you lose the existing infrastructure.
Why it matters
If you're using Cursor, expect extension breakage and workflow changes. This matters because it's the first test of whether users value AI features enough to tolerate losing VS Code's mature ecosystem. It also signals whether future AI editors will fork or build clean-room implementations.
Key details
- •Cursor 3 launched with proprietary 'frontier editor' replacing VS Code codebase
- •VS Code extensions may break or require rewrites for new architecture
- •Trade-off: tighter AI integration and performance vs. ecosystem compatibility
- •Community reaction mixed — some praise speed improvements, others report broken workflows
- •Sets precedent for AI editor strategy: differentiation vs. compatibility
Worth watching
Video data provided by YouTube. Videos link to youtube.com.