OpenAI Cuts Off Cursor on November 12: Read the Change-of-Control Clause
OpenAI just showed every developer what a model supplier exit looks like. On Friday, the company notified SpaceX that it will wind down the contract providing OpenAI models to Cursor, with a proposed shutoff date of November 12, 2026 (Devdiscourse, 2026). OpenAI published the decision in its own statement and said it is giving developers the maximum notice its contract allows (OpenAI on X, 2026).
This is not a product dispute. It is a contract clause firing exactly as written, two weeks after SpaceX closed its $60 billion all-stock acquisition of Anysphere, the company behind Cursor (ExplainX, 2026).
The statement, in full
Section titled “The statement, in full”OpenAI’s statement is short. Here is the core of it:
“Today, we notified SpaceX that we intend to wind down our contract providing OpenAI models to Cursor, with a proposed shutoff date of November 12, 2026. To maximize the time that developers can retain access to our models through Cursor, we are giving the maximum notice provided by our contract.” (Livemint, 2026)
The reason follows in the same statement. OpenAI wrote that it is “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” (Business Insider, 2026). The company also called the decision tough and said it wants its models to stay broadly available to developers (Storyboard18, 2026).
The mechanism: a change-of-control clause
Section titled “The mechanism: a change-of-control clause”The timeline shows a clause doing its job:
| Date | Event |
|---|---|
| April 2026 | SpaceX and Cursor announce a strategic partnership with an option: SpaceX can acquire Cursor for $60B or pay a $10B break-up fee (Dealroom, 2026) |
| June 16, 2026 | SpaceX files to acquire Anysphere in an all-stock deal (ExplainX, 2026) |
| August 14, 2026 | The acquisition closes and Cursor joins the SpaceXAI group (ExplainX, 2026) |
| August 28, 2026 | OpenAI serves notice, invoking the change-of-control provision in its agreement (Devdiscourse, 2026) |
| November 12, 2026 | Proposed shutoff. That works out to 76 days of notice (Livemint, 2026) |
OpenAI’s custom agreement with Cursor carried a cancellation window that opened when ownership changed (AI Tools Recap, 2026). The acquisition triggered it.
The precedent list in OpenAI’s reasoning is specific. After Musk acquired Twitter, the company broke the terms of its OpenAI contract. xAI, now part of SpaceX, admitted violating OpenAI’s terms of service (AI Tools Recap, 2026).
What changes for Cursor users
Section titled “What changes for Cursor users”- GPT models keep working until November 12. Cursor’s site lists OpenAI’s GPT-5.6 Luna, Sol, and Terra models for paid users today (Business Insider, 2026).
- The model menu freezes now. OpenAI will ship no future models to Cursor in the meantime, including Astra, its next model (Business Insider, 2026).
- Anthropic has not said publicly whether Claude stays in Cursor (AI Tools Recap, 2026).
- SpaceX and OpenAI spokespeople did not immediately return press requests for comment (Business Insider, 2026).
The migration path inside the deal is already visible. Cursor’s official account announced it partnered with SpaceXAI to train Grok 4.5, a model built for large codebases and long-running, multi-repository tasks (VentureBeat, 2026). Four days after the close, Cursor shipped Origin, an in-app code hosting platform, and Grok 4.6 reached Amazon Bedrock (ExplainX, 2026).
Why this matters beyond Cursor
Section titled “Why this matters beyond Cursor”SpaceX now holds compute, model, and distribution in one stack. The company owns the Colossus training infrastructure, the Grok model family, and the developer base of a dominant AI coding tool (VentureBeat, 2026).
The tooling layer between model suppliers and developers is being bought, not built. Stripe bought OpenRouter earlier this month (we covered that deal here), and SpaceX bought Cursor. When the aggregator becomes a subsidiary of a supplier or a competitor, suppliers gain a new reason to walk. Ownership changes become outages with a 76-day countdown.
What your team should do now
Section titled “What your team should do now”- Treat model access as a dependency. Pin model IDs in config, log the provider and version behind every call, and alert on changes the way you alert on image digest drift.
- Keep evals provider-neutral. A suite that runs per provider turns a forced migration into a measured comparison instead of a leap of faith.
- Own the routing layer. BYOK or a gateway you control makes a supplier exit a config change, not a rewrite. The Stripe-OpenRouter deal taught the same lesson.
- Read the change-of-control clause. Your own contracts have one. This episode shows the exit fires on ownership, not on failure, and 76 days is what maximum notice looks like.
Model supply chains now behave like every other supply chain. They are single-sourced, exposed to politics, and one acquisition away from a forced migration. Build for that.