OpenAI is cutting Cursor off from its models — the SpaceX acquisition's first real consequence
OpenAI notified SpaceX on 28 August 2026 that it will terminate Cursor's access to its models on 12 November, citing Elon Musk's history of breaking contracts, weeks after SpaceX closed its $60bn acquisition of Cursor-maker Anysphere on 14 August — a concrete example of the vendor-consolidation risk this signal flagged back in July.
2 September 2026
OpenAI has told SpaceX it’s terminating the agreement that lets Cursor use OpenAI’s models, effective 12 November 2026. The notice, sent 28 August, came two weeks after SpaceX closed its $60 billion all-stock acquisition of Anysphere, Cursor’s parent company, folding it into a new SpaceXAI division. OpenAI’s stated reason isn’t commercial — it’s trust: the company points to Elon Musk’s own sworn admission that xAI trained on OpenAI model outputs via distillation, and says it can no longer be confident SpaceX will honour the terms of its model licence.
Cursor’s co-founder was quick to downplay the practical impact, saying OpenAI models made up only around 5% of Cursor’s traffic, with the majority already running on Claude and Google’s models. That’s probably true, and it’s also beside the point. In July we flagged this acquisition as a live case study in AI tool vendor consolidation — the question every buyer should ask when a tool they depend on changes ownership. Six weeks later, that question has a concrete answer: a model provider can and will pull access over a dispute that has nothing to do with the product itself, with real users caught in the middle of a fight they didn’t start.
Why this is worth watching even if you don’t use Cursor
The mechanism matters more than the specific tool. Any AI coding product that licenses models from an external provider rather than owning them outright carries this exposure — a relationship dispute, an ownership change, or a contract renegotiation upstream can degrade or cut off a capability your delivery team relies on, on a timeline you don’t control. Cursor’s users have roughly ten weeks’ notice and other model options already in place; not every vendor’s users would be so lucky.
So what
If a build you’re commissioning depends heavily on one AI coding tool, it’s worth knowing which model providers sit behind it and how exposed that relationship is. A team that works fluently across Claude Code, Cursor, and other tooling can route around a cutoff like this without it touching your delivery. Our AI-assisted development work is built on exactly that flexibility — get in touch if you want a second opinion on how exposed your current stack is.