Scale · founder · 7 min read

OpenAI Is Pulling Its Models Out of Cursor on November 12

OpenAI is ending its model contract with Cursor after the SpaceX acquisition. Here's what actually breaks, when, and what to do about it.

Published September 5, 2026 ·

cursor openai spacex vendor risk model access founders

On August 28, OpenAI published a note saying it intends to wind down the contract that supplies its models to Cursor. The proposed shutoff date is November 12, 2026.

If you use Cursor and you sometimes pick a GPT model from the dropdown, that dropdown gets shorter in about ten weeks. That is the whole practical story. But the reason it’s happening is worth understanding, because it’s the first time an ownership change has visibly reached through and removed a feature from a tool that thousands of founders are mid-build on.

What happened, in order

SpaceX closed its $60 billion all-stock acquisition of Anysphere — Cursor’s parent — on August 14. We covered the deal when it was signed in June and said at the time that nothing changes for you today. That was true then. It stopped being true fourteen days after the close.

OpenAI’s contract with Cursor was a custom agreement, not the standard API terms, and it contained a change-of-control clause: a limited window after new ownership in which OpenAI can cancel. OpenAI used it, and used the latest date the clause allowed rather than the earliest. That detail is doing real work in their post — they’re signalling that this is a decision about SpaceX, not a decision to hurt Cursor’s users.

The stated reason is trust, not money. OpenAI cites two things: that Twitter broke its contract terms after Musk acquired it, and that Musk admitted under oath earlier this year that xAI had violated OpenAI’s terms of service. Twitter and xAI are both under the SpaceX umbrella now. OpenAI also says it will not supply future models to Cursor in the meantime — so GPT-6 Astra, launched September 3, never appears in Cursor’s picker at all.

Cursor’s side: co-founder Michael Truell responded on August 29 saying OpenAI models account for roughly 5% of Cursor’s user traffic, that he’s disappointed, and that the two companies are still talking. Take the 5% as a directional number from an interested party, not an audited one. But it is plausible — Claude models have been the default choice inside Cursor for most of the past year, and Cursor has been pushing its own Composer models hard.

What actually breaks for you

Almost certainly nothing, and here’s why that’s the honest answer rather than a reassuring one.

If you never touched the model picker: nothing changes. Cursor’s Auto routing has been steering most requests to Claude and to Cursor’s own models for a long time. You will not notice November 12.

If you specifically pick GPT models: you lose that option on November 12 and you lose access to anything OpenAI releases before then. Your replacement is Claude Fable 5.1, Gemini 3.8 Flash, or Grok — all already in the picker, all competitive, and in the case of Fable 5.1 currently ahead of Astra on the coding benchmarks anyway.

If you use a bring-your-own-key setup: this is the one genuinely unresolved question. Cursor has long let you plug in your own OpenAI API key and bill yourself directly. Whether that path survives the contract wind-down is not addressed in OpenAI’s post, and neither company has clarified it. If BYOK is load-bearing for you, ask Cursor support directly and get the answer in writing before November.

If you’re on Codex or the OpenAI API elsewhere: untouched. This is about one contract with one distributor.

The part that matters more than the models

The models are replaceable. The precedent isn’t.

Every AI building tool you use is a thin layer over model contracts you cannot see, negotiated between companies whose relationships you have no visibility into. Lovable’s output quality depends on which Claude tier it’s buying. Bolt’s does too. Cursor’s picker depends on four separate supplier relationships, one of which just got cancelled over a corporate feud that has nothing to do with code.

You have been treating “which model does this tool use” as a spec sheet question. It is actually a counterparty question, and counterparty relationships change on timelines you don’t control and for reasons that aren’t about you.

That doesn’t mean you should panic-switch tools. It means two specific, cheap habits are worth adopting:

Know what your tool falls back to. For every builder in your stack, you should be able to answer: if its primary model went away next month, what’s the substitute, and is it good enough? For Cursor the answer is strong — four suppliers, one leaving. For a single-model tool with no picker, the answer might be “nothing,” and that’s worth knowing before it’s tested.

Keep your code where you can move it. This is the same conclusion as our piece on code custody, arriving from a different direction. A tool losing a model supplier is survivable. A tool losing a model supplier while holding the only copy of your repo is a different situation.

What to actually do this week

Nothing urgent. Genuinely. But three things are worth ten minutes:

1. Check whether you use GPT models in Cursor at all. Open the model picker and look at what you’ve been selecting. Most people will find they’ve been on Auto or on Claude for months.
2. If you use BYOK with an OpenAI key, ask Cursor whether it survives. Don’t assume either way.
3. Put November 12 in your calendar if either of the above applies. Nothing to do before then, but you don’t want to discover this on the day.

The uncomfortable read

There’s a version of this story where OpenAI is protecting its terms of service from a company with a documented record of violating them, and that version is well-supported by the evidence they cite. There’s another version where a market-leading model provider used a contract clause to remove itself from a competitor’s product two months after that competitor was bought by a rival lab, and timed it so its newest model never reaches those users at all. Both readings fit the same facts.

What’s not in dispute is the effect on you: the tools you build with are increasingly owned by, or supplied by, a small number of companies that are actively fighting each other. That fight now reaches into your editor. It will do so again.

Sources: OpenAI’s announcement (August 28, 2026), Forbes, DevOps.com, Crypto Briefing on Truell’s response.