What OpenAI Actually Said

On August 28, 2026, OpenAI notified Anysphere — the company that operates Cursor — that it intends to terminate their model supply agreement, effective November 12, 2026. The trigger was SpaceX’s $60 billion acquisition of Anysphere, which closed on August 14. OpenAI said it “cannot be confident” that SpaceX will use its technology within its terms of service, citing what it described as its “experience with Elon Musk’s companies violating contracts.”

The statement specifically referenced Musk’s courtroom admission that xAI trained on OpenAI’s output. That admission, made during litigation between Musk and OpenAI, effectively gave OpenAI the contractual grounds it needed to invoke a trust clause and wind down the relationship.

OpenAI acknowledged it had worked with Cursor for nearly four years, and said it would “support developers through the transition” — a phrase that translates, in practice, to an 11-week window to switch workflows.

Why This Triggered a Trust Clause

The mechanics here matter. Most AI API agreements include clauses that allow either party to terminate if there is a material change in ownership or if the licensee’s use poses reputational or competitive risk to the licensor. SpaceX’s acquisition of Cursor almost certainly tripped both wires.

SpaceX is not a neutral third party. It is controlled by Elon Musk, who is simultaneously running xAI — a direct competitor to OpenAI — and who has been involved in active litigation against OpenAI for more than a year. Allowing Cursor, now a SpaceX subsidiary, to serve GPT models to four million developers while Musk’s other companies litigate and compete against OpenAI is exactly the kind of scenario these clauses are designed to prevent.

OpenAI also said it would not provide future models to Cursor as it winds down the agreement. That detail matters: it is not just a termination of current access, but a foreclosure of any future relationship under SpaceX ownership.

How Much of Cursor Actually Runs on OpenAI Models

The headline sounds alarming, but the operational impact for most developers is limited. OpenAI models account for approximately 5% of Cursor user traffic. The vast majority of Cursor’s inference runs on Claude (Anthropic), Gemini (Google), and Grok (xAI) — all of which remain available and are unaffected by the November 12 cutoff.

That said, the 5% figure is not evenly distributed. Power users who explicitly selected GPT-5.5, GPT-5.6 Sol, or earlier GPT-4o variants as their default model will be directly disrupted. Some enterprise customers have procurement agreements that locked them into OpenAI models for compliance reasons — those teams face real migration work.

Anthropic has already moved to capitalize on the opening. Within days of OpenAI’s announcement, Anthropic extended higher Claude usage limits to Cursor users through an expedited migration offer, positioning Claude Sonnet 5 and Claude Opus 5 as the natural replacements. Our August comparison of Claude Code, Cursor, and Augment Code showed Claude’s models leading on context retention and refactor quality — a meaningful advantage heading into this transition.

What Cursor Developers Should Do Before November 12

The window is 11 weeks, which is enough time to act without panic but short enough that waiting until mid-October is a mistake. Here is the practical checklist:

Audit your default model settings. Open Cursor’s model picker and check which models you have set as defaults for chat, completion, and agent mode. If any are GPT-series models, switch them now. Claude Sonnet 5 is the closest performance match for most tasks; for pure coding speed, Gemini 3.7 Flash is competitive.

Check your personal API key configuration. Cursor lets users bring their own OpenAI API keys. Important nuance: even personal API keys will not override the partnership cutoff for models served through Cursor’s infrastructure. However, if you use a personal key to call the OpenAI API directly via Cursor’s custom endpoint feature, that traffic is independent of the Anysphere agreement. The gap matters — verify which path your key is actually using.

Review enterprise procurement agreements. If your organization signed an enterprise agreement that specifies OpenAI models for compliance, audit, or data-residency reasons, escalate to your vendor management team now. The November 12 date is firm; renegotiating enterprise contracts takes time.

Test your workflows on Claude and Gemini this week. Eleven weeks feels long until you discover that a critical internal tool relies on GPT-specific behavior — formatting quirks, function calling schemas, or system prompt handling that differs between providers. Running a parallel validation now prevents a production surprise in November. Our 5-step Cursor acquisition audit walks through exactly this kind of workflow validation.

The Bigger Picture: Developer Platform Sovereignty

The OpenAI–Cursor split is a preview of a structural problem that will recur throughout the AI tooling ecosystem. Developer tools increasingly depend on model APIs from providers who are simultaneously competitors, investors, or adversaries of the companies that acquire those tools. The Musk–OpenAI relationship is an extreme case, but it exposes the general fragility.

The lesson for developer teams is straightforward: any tool that routes your code, queries, and context through a single model provider carries a supplier concentration risk that has nothing to do with model quality. The teams least disrupted by November 12 are the ones who already used multiple models interchangeably — not because they anticipated this specific event, but because they treated model selection as a changeable configuration, not a fixed dependency.

This also raises a harder question about SpaceX’s intentions with Cursor. SpaceX paid $60 billion for a coding tool with four million users and deep integration into enterprise engineering workflows. It did not buy a model provider. The value is in the editor, the agent infrastructure, the user base, and the enterprise contracts — all of which survive the OpenAI cutoff intact. Whether SpaceX redirects Cursor toward xAI’s Grok models more aggressively going forward is the next question to watch.

Further Reading

• OpenAI’s official statement on ending the Cursor partnership — the primary source, brief and direct.
• CNBC: OpenAI to end model access to Cursor after SpaceX acquisition — solid reporting on the timeline and OpenAI’s stated rationale.
• Tom’s Guide: OpenAI is leaving Cursor — your 3 options — practical breakdown of what individual developers and teams can do before November 12.