OpenAI is walking away from Cursor
OpenAI will cut off Cursor's direct access to its models on November 12, 2026, after SpaceX acquired the coding-assistant company in a deal reported at $60 billion. The move follows SpaceX's launch of an internal AI unit, SpaceXAI, which now owns Cursor outright. OpenAI's contract with Cursor includes a clause letting either side terminate within a limited window after a change of corporate control, and OpenAI is exercising it.
A trust problem, not a technical one
OpenAI's stated reason is not performance or pricing but confidence that SpaceX, under Elon Musk, will actually honor the contract going forward. OpenAI's Thibault Sottiaux summed it up: "It boils down to trust." The company pointed to two prior episodes with Musk-run businesses to justify that position. In December 2022, Musk cut OpenAI's access to Twitter's data, ending a licensing arrangement worth roughly $2 million a year. More recently, Musk has acknowledged using OpenAI's own model outputs to train Grok through a technique called distillation, a practice OpenAI has separately challenged when it accused other companies, including DeepSeek, of doing the same thing.
OpenAI also cited safety concerns tied to an unreleased Musk-side model reportedly codenamed Astra, which OpenAI says has advanced cyber capabilities.
How much this actually changes for Cursor
Despite the dramatic framing, OpenAI's models reportedly account for only about 5% of Cursor's traffic and customer usage today. Cursor will keep offering models from Anthropic, Google, and SpaceXAI's own Grok after the cutoff. OpenAI says it will not block access outright: Cursor users will still be able to reach GPT models by supplying their own OpenAI API keys, and OpenAI's IDE extension will remain available to Cursor. What ends on November 12 is the built-in, direct integration, not every path to an OpenAI model inside the product.
Cursor's co-founder and CEO, Michael Truell, said the company is in talks with OpenAI to try to resolve the dispute before the deadline.
Anthropic moves to fill the gap
Anthropic's leadership has signaled it will commit more compute to supporting Claude models inside Cursor, positioning the company to pick up whatever share of usage shifts away from OpenAI once the direct integration ends. For a coding tool that already supports multiple model providers, a partial exit by one of them is more of a reshuffling than a crisis, but it is a reshuffling other AI labs are clearly ready to exploit.
Old history, new leverage
The dispute sits on top of a much longer-running conflict between OpenAI and Musk. Musk co-founded OpenAI and left its board in 2018 over disagreements about its direction. In 2024 he sued to block OpenAI's conversion from a nonprofit to a for-profit structure, a case a jury ruled against him on in May 2026. Cutting off Cursor's model access is the first time that feud has directly affected a widely used third-party developer product rather than OpenAI's own corporate structure. Where the Twitter data cutoff and the distillation dispute played out mostly as arguments between two companies, this decision reaches into tools that outside developers rely on every day, which is why it registered well beyond the two companies involved.
Why a change-of-control clause matters here
The mechanism OpenAI is using, a termination right triggered by a change of corporate control, is a standard piece of commercial software contracts, meant to let a vendor walk away if a customer is acquired by someone the vendor would not have done business with in the first place. It is rarely exercised this publicly. By invoking it against a company as visible as Cursor, and explaining the reasoning in terms of Musk's personal conduct rather than confidential contract terms, OpenAI turned a routine legal option into a public statement about the two companies' relationship.
What it means for developers
If you use Cursor with OpenAI's models today, budget for a change before November 12: either switch to one of Cursor's other supported providers or plan to supply your own OpenAI API key to keep using GPT models inside the editor. For teams evaluating AI coding tools more broadly, the episode is a reminder that model access inside a third-party product can depend on corporate relationships that have nothing to do with the tool's technical merits, and that relationship can change with an acquisition neither the developer nor the model provider controls.
