Back to articles

19 June 2026 · Aurelius Ivan Wijaya · 5 min read

Cursor, SpaceX/xAI, and the $60B Bet: What It Means for Engineering Teams in Indonesia

On 16 June 2026, SpaceX signed an agreement to acquire Anysphere, the company behind the AI coding tool Cursor, for $60 billion in stock. The deal is agreed, not yet closed (target Q3 2026, pending regulatory approval). Here is what it signals for teams in Indonesia deciding how to build software. It is written by someone who trains those teams as a Cursor Ambassador.

Deal status: SpaceX signed an agreement to acquire Anysphere on 16 June 2026 for $60 billion all-stock. The deal is agreed, not yet closed; target close Q3 2026, pending regulatory approval. This caveat applies to every reference to the acquisition below. Last updated: 19 June 2026.

What actually happened

On 16 June 2026, SpaceX signed an agreement to acquire Anysphere, the company behind Cursor, for $60 billion in all-stock consideration. The deal is agreed but not closed; target close is Q3 2026, subject to regulatory approval. Reports indicate that Elon Musk had merged SpaceX with his AI company xAI earlier in 2026, making this acquisition a move in his broader AI play against Anthropic and OpenAI on the coding tooling front. Cursor has reportedly surpassed $4 billion in annual recurring revenue, which gives some context for a price tag that would otherwise look extraordinary.

Why the price tag is the real signal

Strip the headline and look at what the number represents. Software is shifting from writing code to directing AI agents that write, test, and review it. A $60 billion price tag is the market putting a value on that shift. It is paying for the position a tool holds inside the engineering workflow as teams move from producing code manually to directing agents that produce it. That is the shift worth tracking, because it describes what your engineering team will need to do well in the next few years regardless of which tool ends up in the IDE.

What stays the same for an Indonesian engineering team

Your codebase, your standards, and your review discipline still decide quality. A tool changing owners leaves your team exactly as skilled as it was yesterday. Licences give your team access to a tool; capability is what ships software. The deal does not transfer agentic development skills to your engineers. It does not change how well your team can give an agent useful context, catch what the agent gets wrong, or integrate AI-assisted output into a codebase your team owns and maintains. Those skills come from deliberate practice, not from a vendor announcement.

What a team should actually do now

Treat agentic development as a capability your team builds. Give engineers repetitions at directing agents across a real codebase: setting context, running multi-file edits, reviewing the output before it merges. That is the operating model worth standardizing across the team now, while agentic tooling still sets the fastest teams apart.

If you want to start that process for your engineering team, the Cursor training program at aitraining.id covers the full agentic development workflow, and the AI-Powered Development corporate training is available on-site for teams across Indonesia.

One honest caveat

The deal can still be delayed, restructured, or blocked by regulators. Treat ownership as unsettled until it closes in Q3 2026. The capability case stands either way. A team that knows how to direct AI agents across a codebase keeps shipping regardless of which company owns the tool.

Tooling vendors come and go. A team that can direct agents keeps shipping, and that is the bet worth making.

Author note

Aurelius Ivan Wijaya is a corporate AI trainer in Indonesia and a Cursor Ambassador. He trains engineering teams on agentic development.