OpenAI Is Leaving Cursor After the SpaceX Deal

Matthew Leo · Published August 29, 2026 · AI

Editorial cover for OpenAI leaving Cursor after the SpaceX deal

OpenAI is preparing to stop supplying its models to Cursor after the coding platform’s acquisition by SpaceX, and the most useful question for developers is not who won the latest Musk-versus-Altman argument. It is what happens to their workflows when the contract ends.

OpenAI said on August 28 that it had notified SpaceX of its intent to wind down the agreement that gives Cursor access to OpenAI models. The proposed cutoff date is November 12, 2026, although the companies still have to confirm the final termination date. Cursor was acquired by SpaceX earlier in August after a deal process that began in the spring.

The change does not mean Cursor itself is shutting down, and it does not necessarily mean developers will be unable to use OpenAI models inside the editor. OpenAI is already pointing users toward alternative routes, including bringing their own API key and using the Codex IDE extension.

Why OpenAI is ending the deal

OpenAI’s public explanation is unusually direct. The company says its contract with Cursor includes a limited cancellation window after a change of control and that it does not have enough confidence that SpaceX will use OpenAI technology within its terms.

In its August 28 statement, OpenAI cited previous disputes involving other Elon Musk companies, including contractual issues after Musk acquired Twitter and an earlier terms-of-service violation involving xAI. OpenAI said Cursor itself had not been accused of breaching the current agreement.

That distinction matters. This is not a claim that Cursor secretly misused OpenAI models. It is a decision OpenAI says it is making because ownership changed and because the contract gives it a chance to exit after that change.

Cursor’s own acquisition announcement framed the SpaceX deal around access to much larger computing resources and the ability to build more capable models at lower cost. The company said Grok 4.6 was an early example of what the combined organization could build.

Cursor users are not being cut off tomorrow

The proposed transition runs until November 12. OpenAI says Cursor can continue using the OpenAI models it already has access to during that period, unless Cursor chooses to end access earlier.

That gives developers time to check whether any part of their workflow depends specifically on an OpenAI model rather than on Cursor as a product.

If you use Cursor’s automatic model selection and rarely pay attention to the underlying provider, this is a good moment to look. Teams that have standardized prompts, coding agents or evaluations around a specific model should test alternatives before the deadline instead of waiting for behaviour to change in production.

You may still be able to use OpenAI models in Cursor

OpenAI’s updated Cursor support guidance lists several ways developers can continue using its models after the direct partnership winds down.

The most obvious is to bring your own OpenAI API key. OpenAI says that can be used with Cursor’s local Chat and Agent features, with usage billed at normal OpenAI API prices.

There is also the Codex IDE extension, which can run directly inside Cursor using a ChatGPT subscription or an OpenAI API key. OpenAI also points to compatible gateway providers such as Azure and Amazon Bedrock where appropriate.

Those routes are not identical to Cursor bundling OpenAI access into its own product. Billing, model availability, rate limits and enterprise controls can differ. A team that cares about predictable cost should compare those details before assuming a bring-your-own-key setup is a drop-in replacement.

The bigger issue is how dependent coding tools are on rival model providers

Cursor became popular partly because it did not force developers to bet on one model company. Users could choose between different providers while keeping the editor and workflow familiar.

That flexibility now has a business risk attached to it. A coding platform can build a strong product around several outside models, but access to those models still depends on contracts between companies that may later become competitors, acquisition targets or strategic enemies.

The SpaceX acquisition makes that tension impossible to ignore. SpaceX now owns a coding platform while also controlling xAI and its Grok models. OpenAI has its own coding products and model ambitions. Anthropic competes with both while supplying models used in coding tools. Everyone wants distribution, but everyone also wants to own more of the stack.

For developers, model choice increasingly looks less like a permanent product feature and more like a dependency that can change after a merger, licensing dispute or pricing decision.

What teams using Cursor should check now

This is bigger than an OpenAI–Musk feud

The personalities make this story easy to frame as another chapter in the long dispute between Elon Musk and OpenAI. That is part of it, but stopping there misses what matters to the people actually using the software.

AI coding products are becoming platforms built on other platforms. A change in ownership can therefore reach all the way down to the model a developer uses to review a pull request on Monday morning.

Cursor still has months to negotiate, and OpenAI says the final date is not yet confirmed. The companies could still reach a different arrangement.

But developers should treat the announcement as a reminder that model portability matters. The safest workflow is one that can survive a provider changing its mind.

Tags: OpenAI, Cursor, SpaceX, AI coding, Analysis

Read on Mapletechie