Kilo Bets on VS Code and Model Freedom Amid Roo Shutdown, Cursor Deal
RooCode sunsets VS Code extension May 15; Kilo rebuilds on open core for agentic coding. Cursor's SpaceX ties risk model lock-in—choose agnostic tools like Kilo for flexibility as best models shift weekly.
RooCode Exit Validates Agentic VS Code—Kilo Steps In with Unified Core
RooCode, with millions of installs, pioneered agentic coding in VS Code: custom modes (architect, code, debug), file/terminal access for real work beyond autocomplete. It sunsets its VS Code extension, Cloud, and Router on May 15, refunding balances and archiving the repo, shifting to remote agents.
Kilo credits Roo's influence but rejects IDE obsolescence. They rebuilt their VS Code extension on the open code server core powering their CLI/cloud agents, enabling seamless context across environments. Key features: true parallel execution, sub-agent delegation, agent manager for multiples, inline diff review with line-level comments, persistent sessions between terminal/editor.
Migration from Roo is straightforward due to shared ancestry; Kilo provides resources for modes, settings, model profiles, MCP servers, rules files. Outcome: Developers retain interactive editor for inspection, diffs, local commands alongside remote agents for long-running tasks—hybrid wins over IDE-vs-cloud.
Cursor-SpaceX Deal Signals Model Lock-In Risks for Users
SpaceX holds option to acquire Cursor for $60B later this year or pay $10B for joint work, tying it to XAI. Kilo warns this turns coding tools into model distribution layers: OpenAI (Codex), Anthropic (Claude Code), Google (coding products), now SpaceX/XAI-Cursor.
Incentives favor pushing proprietary models via defaults, pricing, latency—even subtly. Cursor thrived on flexibility (Claude for refactors, GPT for review, Gemini cheap, Grok fast, Qwen/Kimi low-cost). Post-deal, Claude access could degrade, per Anthropic's Windsurf cutoff amid OpenAI rumors—"don't arm competitors."
Positive spin: Partnership boosts Cursor's compute for bigger models. Skeptical: XAI seeks dev adoption to rival OpenAI/Anthropic. Users lose if tied to one provider as top models rotate weekly.
Build Portable Workflows with Agnostic Tools
Kilo positions as independent: VS Code-focused post-Roo, model-agnostic vs Cursor/XAI. Alternatives: Kline, OpenCode, Aider—bring-your-own-key, switch providers.
Market consolidates: independents go cloud (Roo), model-tied (Cursor), or agnostic platforms (Kilo). Advice: Avoid single-stack dependency—use normal repos, exportable settings, changeable models. Pay for tools/ecosystems minding lock-in. Test daily: stability, cost, control, iteration. Hybrid future (editor + cloud) thrives with model freedom for optimal task-model pairing.