OpenAI Is Pulling Its Models Out of Cursor, and Musk Is the Reason It Gives

If you open Cursor every morning with an OpenAI model selected in the picker, you have until November 12 to choose something else. OpenAI is winding down the contract that supplies its models to Cursor, and the reason has nothing to do with Cursor's code or its bill.

OpenAI laid it out in its own post on August 28: "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." Cursor now belongs to SpaceX, which also owns xAI. Both answer to Elon Musk, and OpenAI would rather not hand him the keys.

Why OpenAI says it's doing this

OpenAI's argument is about Musk's other companies. It wrote that it 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." It cited two things by name: after Musk bought Twitter, now part of SpaceX, the company "broke the terms of our contract (alongside many others)," and "Under oath earlier this year, Musk admitted that xAI, now also part of SpaceX, had violated OpenAI's terms of service."

There is also a model OpenAI wants kept away from the new owner. "As AI capabilities advance, we also have a new level of accountability to ensure our upcoming model, Astra, is being used in accordance with our terms," the post says, before landing on its compromise: "we've decided to hold the contract cancellation to the latest date we can while not providing future models to Cursor." Cursor keeps what it already has until the shutoff and gets nothing new in the meantime. OpenAI says it is giving "the maximum notice provided by our contract" so developers keep access as long as possible, and that it is "ready to go above and beyond to support them" through the switch. What that support looks like in practice, it didn't say.

What actually breaks for you

Less than the headline suggests, if Cursor's own numbers hold. CEO Michael Truell said on X that OpenAI models account for roughly 5% of Cursor's AI traffic. The rest runs on models from Anthropic, Google, xAI and Cursor itself, none of which are touched by this. If you already default to Claude in the picker, your Tuesday looks identical.

If you are in that 5%, the obvious workaround is thinner than it sounds. You can drop your own OpenAI API key into Cursor and keep using its chat models, but per Cursor's own documentation, "Tab completion continues using Cursor's built-in models." The autocomplete that makes Cursor feel like Cursor was never running on your key in the first place. And bring-your-own-key means paying OpenAI per token on top of whatever you already pay Cursor.

Cursor is not thrilled

Truell's reply on X read like a supplier relationship ending badly. "Cursor was one of the very first users of OpenAI, we've worked closely with their team for years, and we've trusted their platform to be neutral infrastructure for our business," he wrote. A model API looks like a utility right up until you remember it's a contract, and contracts have a counterparty with opinions about who owns you.

Anthropic moved fast. Co-founder Tom Brown posted that Cursor has been a reliable partner since Sonnet 3.5 and that Anthropic will increase compute to support Claude models in Cursor. Neither SpaceX nor Musk had issued a public response as of this writing.

Who should be paying attention

If you're a solo developer on Cursor's defaults, this is a change in the model picker and a mild annoyance. If you run a team that pinned OpenAI models into a specific workflow, code review, agents, scripted jobs, you have about ten weeks to test replacements and update whatever you standardized on. Ten weeks is enough time to be picky about the replacement.

Cursor hedged early by supporting several providers, which is why the number in play here is 5% and not 60%. Plenty of AI products run on a single vendor's API, and that vendor often sells something that competes with them. This is a cheap week to find out what your own fallback actually looks like.