In this video, I'll be talking about Kilo’s two new blog posts, one about Roo Code shutting down its VS Code extension and another about Cursor’s ties to SpaceX and xAI, and what both of them mean for the future of AI coding tools, VS Code, and model freedom.

--
Key Takeaways:

🚀 Kilo’s first post reacts to Roo Code sunsetting its VS Code extension, cloud, and router on May 15th.  
🧩 Roo helped popularize agentic coding features like custom modes, file access, terminal access, and autonomous task execution.  
🛠️ Kilo says it rebuilt its VS Code extension from the ground up on the OpenCode server, with support for parallel execution and subagent delegation.  
💡 The main message is that the editor still matters, even as cloud agents continue to grow in popularity.  
📈 The second post focuses on Cursor’s reported deal with SpaceX, which may give SpaceX the right to acquire Cursor later this year.  
🔒 Kilo warns that when a coding tool gets tied to a model provider, users may lose flexibility over time.  
🤖 Model freedom matters because the best AI model for coding can change from week to week depending on the task.  
📦 The broader theme is that AI coding tools are increasingly being pulled toward cloud platforms, model labs, or closed ecosystems.  
✅ Kilo is positioning itself as the independent, model-agnostic middle layer for developers who want flexibility and control.

AICodeKing

RooCode is sunsetting its VS Code extension, cloud, and router on May 15th, while Cursor is reportedly being acquired by SpaceX (with a $60B option or $10B partnership deal tied to XAI). Kilo published two blog posts reacting to both events, positioning itself as the independent, model-agnostic alternative that stays committed to VS Code. The broader concern raised is AI coding tool consolidation: as model labs acquire or partner with coding tools, model flexibility for users may erode over time. The Windsurf/Anthropic precedent — where Claude access was cut when OpenAI acquisition rumors surfaced — is cited as a warning. The recommendation for developers is to keep workflows portable, prefer tools that allow model switching, and avoid lock-in to any single AI stack.

RIP Roo & Cursor: END OF AN ERA!