OpenAI cuts off Cursor after SpaceX acquisition, citing Musk's history of breaking contracts

The timeline is straightforward, yet every step has gripped the AI industry. On June 16, 2026, days after its IPO, SpaceX announced it would acquire Cursor — the AI coding tool founded by former Google employees — in a stock deal valued at roughly $60 billion, positioning it to compete head-on with products like GitHub Copilot. On August 15, SpaceX formally closed the acquisition. OpenAI's contract contained a critical clause: when Cursor underwent a change of control, OpenAI had a limited window to terminate the agreement. OpenAI says it chose to exercise that right at the latest date allowed under the contract rather than cutting off access immediately, to give developers as much time as possible to retain access to OpenAI models.

In a statement on X, OpenAI wrote: 'We're ending our partnership with Cursor following its acquisition by SpaceX. Under our proposal, Cursor's direct access to our models would end on November 12. We know that the people most affected by this decision are the developers who rely on OpenAI models in Cursor.' The statement then offered the core rationale: 'We are making this choice because we cannot be confident that SpaceX will use our technology within our terms of service, based on our experience with Elon Musk's companies violating contracts.' OpenAI pointed to two specific incidents: Twitter, which Musk acquired in 2022 and which is now part of SpaceX, previously violated the terms of its agreement with OpenAI; and Musk admitted under oath earlier this year that xAI — his AI company, now also part of SpaceX — had violated OpenAI's terms of service.

The way OpenAI framed the matter internally is clear from one executive's remarks. Thibault Sottiaux, OpenAI's VP of product, said in response: 'It boils down to trust.' He stressed that users who access GPT models through Cursor can still use their own OpenAI API keys, and OpenAI will continue to provide access through its IDE extensions for Cursor. In other words, this is not a total ban on developers — it cuts off Cursor as the middleman channel for direct model access. At the same time, OpenAI framed the decision as a safety issue: with the upcoming Astra model reportedly possessing advanced capabilities, OpenAI says there is 'a new level of accountability' to ensure partners comply with the terms of service — a loaded implication for a company that has spent years warning about AI risks. Cursor co-founder Michael Truell responded quickly, saying OpenAI models accounted for only about five percent of Cursor's AI traffic, that the company is in talks with OpenAI to find a solution, and that 'Cursor was one of the very first users of OpenAI, we've worked closely with their team for years.'

The most intriguing aspect of this episode is how neatly it echoes the industry's own history. In June 2025, Anthropic blocked the coding tool Windsurf from accessing its Claude models after reports surfaced that OpenAI wanted to acquire Windsurf; in August 2025, the tables turned when Anthropic revoked OpenAI's API access over unauthorized use of Claude for benchmarks. Now OpenAI has done the same to Cursor. In the AI coding tool arena, the power relationship between 'model providers' and 'tool vendors' has never been clearer: whoever controls the models controls the lifeline. For developers, this is also a wake-up call — when choosing an AI coding tool, the stability of the model supply chain behind the tool is becoming just as important as functionality. The outcome of negotiations between Cursor and OpenAI will serve as a case study for how the industry resolves 'model cut-off' standoffs.

For ordinary AI users, the most important takeaway is that competition in the AI coding tool market is no longer a single-dimensional battle over 'whose model is smarter.' It has become a multi-front contest of model capability, supply chain stability, and ecosystem lock-in. OpenAI's cut-off of Cursor is both a business decision and a strategic declaration — it is willing to sacrifice a revenue-generating partnership to defend the authority of its terms of service. For developers, the biggest lesson may be: don't bet your entire workflow on a single model vendor. Multi-model, multi-tool redundancy is moving from 'best practice' to 'survival necessity.'