OpenAI told SpaceX on 28 August 2026 that it intends to wind down the contract supplying OpenAI models inside Cursor, with a proposed shutoff date of 12 November 2026. The trigger was SpaceX’s $60bn acquisition of Cursor, which closed on 14 August — OpenAI’s stated reason is that it can’t be confident SpaceX will use its technology within OpenAI’s terms of service, citing prior experience with Elon Musk-owned companies. After the shutoff, OpenAI models stay reachable inside Cursor only through bring-your-own API key, the separate Codex IDE extension, or third-party AI gateways — not as a built-in, managed option.
This is a genuinely different kind of risk to the usual “which model is best this month” question. It’s a reminder that the AI coding tool a team builds its workflow around sits on top of commercial relationships between vendors that can change — or end — for reasons that have nothing to do with product quality or your project. A tool’s ownership structure and the model-supply agreements underneath it are now a legitimate part of technical due diligence, not just a licensing footnote.
Why this is worth flagging beyond the Cursor/OpenAI specifics
Every AI-assisted development stack now depends on a chain of vendor relationships — the coding tool, the model provider, sometimes a cloud intermediary — and any link in that chain can break with weeks of notice, not years. Teams that built deep, tool-specific workflows around one vendor’s default model integration are more exposed than teams that treat model access as swappable by design.
So what
If your development team or partner relies on a single AI coding tool’s built-in model access, ask what happens if that specific integration disappears — as Cursor users are now finding out with eleven weeks’ notice. We build AI-assisted workflows designed to route around a single vendor dependency rather than depend on one. See our AI-assisted development approach, or get in touch if you want your team’s tooling risk reviewed before it becomes a deadline.