OpenAI Winds Down Cursor Models After the SpaceX Deal

A commercial contract that put frontier models inside a third-party editor now has a published wind-down clock. OpenAI's August 28, 2026 company post says the lab notified SpaceX that it intends to stop supplying OpenAI models to Cursor, with a proposed shutoff date of November 12, 2026. That is a vendor-to-vendor supply contract, not a ChatGPT outage and not an API deprecation. If you call gpt-5.6-sol on OpenAI's own API, this post does not shut you off. If you pick GPT-5.6 Sol, Terra, or Luna inside Cursor, it does.

The official wording is blunt about why. OpenAI writes that it cannot be confident SpaceX will use the technology within its terms of service, "based on our experience with Elon Musk's companies violating contracts." The same post says the custom Cursor agreement gives OpenAI a limited window to cancel after a change of control, and that it is using the maximum notice that contract allows. Reuters, writing the same day, reported the SpaceX purchase of Anysphere (Cursor's parent) as a $60 billion all-stock deal agreed in June and completed earlier in August, and quoted Elon Musk responding on X: "I couldn't care less." Cursor co-founder Michael Truell, now a SpaceX executive, said on X that the company was speaking with OpenAI to resolve the issue, per that same Reuters report.

What the official post actually commits to

Three operational facts sit in OpenAI's own text. First, notice went to SpaceX, not to a public deprecation calendar on the API. Second, the proposed shutoff is November 12, 2026. Third, OpenAI will not provide future models to Cursor in the meantime, and it names the upcoming model Astra as a reason it wants extra accountability on terms. The lab also says it has worked with Cursor for nearly four years and that the people most affected are developers who rely on OpenAI models inside that editor. It promises to "go above and beyond to support them" during the transition. It does not publish a migration checklist, a BYOK path, or a named Codex/ChatGPT bundle as the replacement. Treat the support sentence as intent, not as a product you can click today.

Two earlier episodes are cited as the basis for the distrust. After Musk acquired Twitter, now part of SpaceX, OpenAI says the company broke the terms of its contract. Separately, the post says Musk admitted under oath earlier this year that xAI, now also part of SpaceX, had violated OpenAI's terms of service. Those claims are OpenAI's. They are the stated grounds for pulling a change-of-control clause, not findings of a court in this announcement. I am not going to relitigate the trial here. The contract mechanic that matters for a Cursor user is simpler: a change of control opened a cancellation window, and OpenAI is using it.

"We've decided to hold the contract cancellation to the latest date we can while not providing future models to Cursor."

That line is from the same August 28 post. Read it as two clocks, not one. Existing OpenAI models inside Cursor are proposed to keep running through November 12. New OpenAI models, including Astra, are not promised to Cursor at all. If you were waiting for Astra in the Cursor model picker, this post is the no.

November 12 is proposed, not confirmed

OpenAI's Help Center article on using OpenAI models in Cursor is more cautious than the company blog. It says OpenAI is planning to wind down the contract, has proposed a transition period of November 12, 2026, would continue providing Cursor access to the OpenAI models it uses today during that period, and that Cursor may choose to end access sooner. It also says the official termination date will be shared once both companies confirm it. So the date on the blog is OpenAI's proposed end of the notice window, not a mutually signed cutover. Plan against November 12. Do not treat it as a guarantee that the models stay up through that morning, and do not treat it as a guarantee they vanish that night.

Reuters dated the announcement August 28 and noted Anthropic co-founder Tom Brown saying Anthropic planned to increase compute to support Claude models in Cursor. That is a capacity comment from a rival supplier, not a Cursor changelog. It does not move OpenAI's date. It does tell you Claude is the supplier that just said, on the record, it intends to put more compute behind the same editor.

What Cursor still lists today

Nothing has been removed from Cursor's public model catalog as of this writing on August 30, 2026. The live Cursor Models & Pricing page still lists GPT-5.6 Luna, GPT-5.6 Terra, and GPT-5.6 Sol under provider OpenAI, in the Other Models pool. The same three rows appear on OpenAI's API pricing table at matching short-context standard rates. I am quoting both pages because a Cursor invoice and an API invoice are different bills; on these three models, the published per-million-token numbers currently agree.

Numbers are from Cursor's models page and OpenAI's API pricing table, both fetched August 30, 2026. OpenAI's table marks Sol's $4/$20 row as promotional pricing available at least through November 21, 2026. Cursor's Sol row carries the same promotional note through November 21, plus a Fast mode at 2x those rates, long context up to 1M tokens with 2x input pricing, and a requirement for Max Mode on legacy request-based plans. I am not inventing a Cursor-specific discount on top of that. If the two live pages ever diverge, use the page that bills you.

Two calendars now sit next to each other. OpenAI's Sol API promo runs at least through November 21. The Cursor supply contract is proposed to end November 12. Those are not the same clock. Direct API callers keep the promo for as long as the API table says so. Cursor users keep Sol only for as long as the Cursor contract and the Help Center confirmation allow. A nine-day gap between those dates is not a bug in either document. It is two products.

Which Cursor usage this actually hits

Cursor's own pricing page splits usage into two pools. Cursor Models covers Cursor Grok 4.6, Grok 4.5, and Composer 2.5. Other Models is the pool for third-party models, charged at the model's API price. Pro at $20/month, Pro Plus at $60/month, and Ultra at $200/month include both pools, per that page. Start, the India-only plan at ₹649/month tax inclusive, includes the Cursor Models pool and does not include Other Models. GPT-5.6 Sol, Terra, and Luna sit in Other Models. Grok and Composer do not. OpenAI's wind-down post is about the contract that provides OpenAI models to Cursor. It does not mention Grok, Composer, or Claude. Those rows are different suppliers on Cursor's catalog.

So the blast radius is the OpenAI rows in the Other Models pool, plus whatever Auto routing currently sends to those rows. It is not "Cursor stops working." It is not "Grok 4.6 leaves the editor." It is not "Claude leaves the editor." Teams on Start never had the OpenAI pool in the first place. Teams that already live on Claude, Grok, or Composer will feel this as a missing picker option, not as a dead editor. Teams that pinned Sol or Terra as the daily driver need a fallback before the confirmed date, not after.

Direct OpenAI surfaces are a separate stack. ChatGPT, the API, and Codex are not this Cursor contract. The Help Center article is titled "Using OpenAI models in Cursor" for a reason. If your workflow is already Codex CLI, ChatGPT, or a raw gpt-5.6-sol call, OpenAI's August 28 post does not describe shutting those off. If your workflow is "the model picker inside Cursor, set to Sol," it does.

What to do before the date

First, inventory. Look at the last two weeks of Cursor usage, not at the plan name on the invoice. Note which requests were Sol, Terra, Luna, Claude, Grok, Composer, or Auto. If Auto is in the mix, assume some share already lands on OpenAI until you prove otherwise. Cursor documents Auto as billing at the list price of the model each request is routed to. A team that "doesn't use OpenAI" because nobody types the name in the picker can still be on Sol through Auto.

Second, pick a fallback that is already in the editor. Claude is the supplier that, per Reuters, said it would increase compute behind Cursor the same day. Grok 4.6, Grok 4.5, and Composer 2.5 are the Cursor Models pool on the live pricing page, and they are not OpenAI rows. I am not ranking those models. I am pointing at which catalog lines are not the contract being cancelled.

Third, keep a path that does not depend on Cursor's OpenAI contract at all. That is OpenAI's own API, ChatGPT, or Codex, billed on OpenAI's table, or another editor. The August 28 post does not publish a recommended destination. It says OpenAI is ready to support developers through the transition. Until that support is a documented product, the durable path is one you already control: an API key, a second editor, or a model already in Cursor that is not on the OpenAI row.

Fourth, watch two pages, not Twitter. The Help Center article is where OpenAI said it will publish the official termination date once both companies confirm it. Cursor's models page is where a removal would show up as a missing row. If the Help Center still says "proposed" on November 11, you do not have confirmation. If Cursor's catalog drops the GPT-5.6 rows earlier, believe the catalog.

The useful question is not whether OpenAI and Musk are going to make peace in public. The useful question is whether your team still has an OpenAI model in the Cursor picker on a date both companies have actually confirmed. Until that confirmation lands, November 12 is the planning date OpenAI published, Cursor still lists Sol, Terra, and Luna, Claude is the supplier that said it would add compute, and the Cursor Models pool is the set of in-editor options this contract does not name.