August 29, 2026. On August 28, OpenAI notified SpaceX that it intends to wind down the contract that supplies OpenAI models to Cursor, the most widely used AI code editor, with a proposed shutoff date of November 12, 2026. If your team or your agency's developers write software in Cursor with GPT models selected, you now have a hard date: 76 days from the notice to migrate those workflows or accept whatever model menu the new owner stocks. The larger lesson lands on every business that runs on rented intelligence, not just programmers. Model access is a commercial contract with exit clauses, and this week one of those clauses fired in public.
What Happened: From $60B Close to Model Shutoff in 14 Days
- August 14: SpaceX completed its all stock acquisition of Anysphere, the company behind Cursor, in a deal valued at $60 billion and confirmed in an SEC Form 8-K, with roughly 391 million SpaceX Class A shares issued and analysts calling it the largest startup acquisition on record. Cursor became a wholly owned subsidiary inside the rebranded SpaceXAI division, alongside xAI, with access to the Colossus supercomputer. CNBC had reported the deal when it was announced in June.
- August 26: SpaceXAI announced that Grok Bot is now included with SuperGrok, Cursor Pro, and all Cursor Teams plans, bundling its own always on agents into the product it had just bought.
- August 28: OpenAI notified SpaceX it will cancel the model supply agreement, invoking a change of control window in the contract. Current models stay available until the proposed November 12 shutoff, and future models, including OpenAI's upcoming Astra generation, will not come to Cursor at all. OpenAI says it gave the maximum notice its contract allows.
OpenAI's stated reason is trust. It says it cannot be confident SpaceX will use its technology within its terms of service, pointing to Twitter breaking an OpenAI contract after Musk acquired it, and to Musk acknowledging under oath earlier this year that xAI had violated OpenAI's terms. Those are OpenAI's claims and SpaceX will contest the framing. The commercial mechanics, however, are not in dispute: the contract contained a change of control clause, ownership changed, and the clause was exercised.
The Two Day Tell: The Replacement Was Staged First
Put the dates side by side and the sequencing is the story. The Grok Bot bundle landed in Cursor plans on August 26. OpenAI's cancellation notice arrived on August 28. The replacement was on the shelf two days before the removal was announced, which tells you both sides had already modeled this outcome. When the deal closed, Morgan Stanley kept a $300 base target on SpaceX stock and projected the Cursor acquisition could drive up to $13 billion in revenue by 2027, per Investing.com. Those numbers only work if Cursor's developer base converts to Grok models. Cursor does not lose its editor when OpenAI walks. Its users lose a model option, and the new owner gains a captive distribution channel for its own stack, a shift we flagged when Grok Bot expanded to Cursor plans.
Model Access Is a Contract, Not a Utility
Most operators treat model access like electricity: always there, interchangeable, someone else's problem. It behaves more like a commercial lease with a landlord who can decline to renew. This is not even the first disappearance this month. OpenAI shut down its Atlas browser in August on roughly five weeks of notice. The difference is that Atlas was OpenAI's own product to retire. Cursor is a third party product whose model supply got cut upstream. Every SaaS tool your business relies on that advertises GPT, Claude, or Gemini inside sits on the same kind of supply agreement. When ownership changes, strategy changes, or a dispute erupts, the model underneath your workflow can be swapped or removed on 60 to 90 days of notice, sometimes less, and you are not a party to any of the contracts that decide it.
What It Means for Operators: The Vendor Risk Playbook
Four moves, none of which require a legal department. First, build a model bill of materials: list every workflow, automation, and tool your business runs, and write down which model actually powers each one. Most owners cannot answer this today, and you cannot manage a dependency you have not named. Second, test a second model before you need it. Abstraction layers make models swappable in an afternoon when they are designed in from the start, and a painful rebuild when they are not. We build client systems model agnostic by default at our AI automation practice for exactly this reason. Third, read the paper. Vendor marketing says partnership, the binding terms say termination for convenience, change of control, and notice periods. The gap between those two documents is where this week's news lived. Fourth, own your side of the stack: prompts, evaluation sets, workflow definitions, and exported data should live in your accounts, not inside a tool that can vanish. If nobody on the team can carry that audit, a short engagement with a dedicated AI engineer is cheaper than a forced migration on a deadline.
If Your Team Runs on Cursor, Do This Before November 12
Check which models your developers actually default to, because habit is the real dependency. Run a one week bake off of the alternatives on your own repository, not on benchmarks. Grok models are now bundled into Cursor plans, other providers had announced no comparable wind down as of publication, and OpenAI says it is ready to go above and beyond in supporting affected developers through the transition. Note that November 12 is OpenAI's proposed date, so build your plan to be done by early November rather than betting on an extension. If a client contract or compliance requirement names a specific model, flag it this week, because renegotiating that language takes longer than switching editors.
The Bigger Picture: Consolidation Raises the Stakes
xAI joined SpaceX in February. Cursor followed in August. The result is a vertically integrated stack of compute, models, agents, and now the editor developers sit in all day, competing with rivals assembling similar towers. More consolidation means more change of control events, more bundling, and more sudden menu changes at every layer beneath your business. The answer for a small company is not to avoid AI vendors. It is to price the exit before you sign, keep a tested second option warm, and treat every model in your stack as a supplier relationship rather than a law of nature. The teams that internalized that lesson this week got it for free. The teams inside Cursor on GPT models got it with a 76 day fuse attached.
Frequently Asked Questions
OpenAI says it cannot be confident SpaceX will use its technology within its terms of service, citing Twitter breaking an OpenAI contract after Musk acquired it and Musk acknowledging under oath that xAI had violated OpenAI's terms. The contract contained a change of control clause that OpenAI invoked after SpaceX completed its $60 billion acquisition of Cursor's parent company Anysphere on August 14, 2026.
OpenAI proposed a shutoff date of November 12, 2026, which it says reflects the maximum notice period its contract allows. Current OpenAI models remain available in Cursor until then, but future OpenAI models, including the upcoming Astra generation, will not be offered in Cursor at all.
No. The wind down applies to the supply contract that puts OpenAI models inside Cursor. Businesses using ChatGPT, the OpenAI API directly, or OpenAI models inside other tools are not affected by this specific decision, though the episode shows how model access inside any third party tool depends on contracts between vendors.
AI vendor lock-in is when your workflows, automations, or products depend on one provider's model in a way that makes switching slow and expensive. It matters because model access is governed by commercial contracts with termination and change of control clauses, so the model under a workflow can be removed on 60 to 90 days of notice through decisions you are not a party to.
Keep a model bill of materials listing which model powers each workflow, build automations behind an abstraction layer so models are swappable, test a second model before you need it, and keep prompts, evaluation sets, and exported data in your own accounts. Designing systems model agnostic from day one is far cheaper than a forced migration on a deadline.
Yes. Cursor keeps its editor and its other model options, and SpaceXAI has bundled Grok Bot and its Grok models into Cursor Pro and Cursor Teams plans. What changes is the model menu: OpenAI models are scheduled to leave on the proposed shutoff date, so teams that default to them need a tested alternative before November.