SpaceX says it has agreement to acquire Cursor for $60B

Deal Structure and Terms

  • SpaceX announced it has the right to acquire Cursor later this year for $60B, or alternatively pay $10B “for our work together.”
  • Several readers stress this is not a completed acquisition but an option plus a large collaboration/services commitment, likely paid partly in compute credits or stock rather than cash.
  • Some interpret it as 3–4% of SpaceX equity at rumored IPO valuations rather than $60B cash.

Valuation and Financial Engineering Concerns

  • Very broad skepticism that Cursor is worth anything close to $60B; comparisons are made to Twitter’s ~$44B purchase price and WhatsApp’s $19B.
  • Multiple commenters suspect the number is about inflating SpaceX/xAI’s story and IPO valuation, not intrinsic value.
  • Others see the $10B as a real “breakup fee” and the $60B option as unlikely to be exercised, mainly useful as a headline number.

Strategic Rationale Theories

  • Pro- deal arguments:
    • SpaceX/xAI has massive GPU capacity but weak coding models and little enterprise penetration; Cursor has coding-agent expertise, an RL stack, and enterprise customers.
    • Vertical integration: tie Cursor’s harness and data to Grok and Colossus compute, similar to how OpenAI and Anthropic ship their own coding tools.
  • Skeptical takes:
    • Could have built or poached a similar IDE team far cheaper; smells like bailout/financial engineering.
    • Some frame it as part of a broader “Elon conglomerate” shell game or narrative construction (space datacenters, Dyson-sphere-level ambitions).

Cursor’s Product, Models, and Moat

  • Cursor praised for: agentic coding harness (plan/debug modes), good token efficiency, broad model choice, solid enterprise adoption, and Composer 2’s price/performance.
  • Criticisms: clunky/buggy IDE, heavy resource usage, unclear long-term moat (“a VS Code fork”), Composer 2 seen as just a heavily RL-tuned Kimi open model.
  • Reported metrics (ARR, DAU) are cited but also questioned; business may depend on subsidized or thin-margin inference.

Competitive Landscape and Developer Sentiment

  • Many commenters say personal and org usage has shifted from Cursor to Claude Code, Codex, Copilot, Zed, and other TUIs/IDEs.
  • Others argue Cursor remains the best non-lab harness and is still widely used in enterprises, though consumer mindshare has faded.
  • Several immediately vow to cancel Cursor due to Musk’s involvement and ask for alternatives (Claude Code, Codex, OpenCode, Zed, JetBrains, etc.).

Governance, Ethics, and Trust

  • Strong discomfort with Musk’s politics, X’s content issues, and his history with contracts; some enterprises are said to avoid Grok/xAI for IP and reputational reasons.
  • Concern that SpaceX + xAI + X + Cursor consolidation, plus index fast-tracking, offloads risk onto passive investors and entangles public capital in opaque structures.
  • Debate over whether the deal is primarily about data (developer code and interaction logs) despite Cursor’s stated privacy modes; some are skeptical those guarantees would hold.