OpenAI said on August 28, 2026 that after SpaceX acquired Cursor, it notified SpaceX of a plan to wind down its contract to provide OpenAI models to Cursor. The proposed shutoff date is November 12, 2026. OpenAI says it is giving the maximum notice allowed by the contract so developers have more time to keep using the current models. This is not an immediate cutoff, and it is not an announcement that Cursor as a product is shutting down; it is a transition in the model-supply relationship.
OpenAI's stated reason is that, based on its prior experience, it cannot be confident SpaceX will use the technology within the terms of service. The statement refers to change-of-control cancellation terms and OpenAI's accountability for how future models are used. Those are OpenAI's public assertions. This article does not treat the contract dispute as an independently adjudicated fact, nor does it infer what will happen to other Cursor or SpaceX products.
The impact on AI coding workflows is that developers depend on a chain rather than a single model. The chain includes the editor, agent harness, model provider, account permissions, and contract. If a provider changes availability after a change of control, the engineering task is not just switching a model name. Teams may need to retest prompt behavior, tool permissions, context retention, cost, data-processing terms, and CI or development-environment integrations.
OpenAI says large partnerships typically use custom contracts to ensure terms compliance and safety at scale. It also expresses respect for the Cursor team and product and says it is ready to support affected developers. The statement does not provide Cursor's alternative-model plan, a user migration path, or independent verification, so the practical outcome depends on later notices from the parties and on each developer's configuration.
A practical response is to treat the model provider as a replaceable infrastructure dependency. Teams can keep a minimum viable fallback model for critical workflows, maintain a representative coding-task test set, record agent tool calls and approval points, and isolate provider-specific prompts and settings. This is not a claim that every acquisition ends a service. It is recognition that once agent work becomes part of everyday development, provider policy changes become engineering risk.
As of OpenAI's August 28 statement, November 12 is a proposed date, not a completed shutdown. Developers should follow later notices from Cursor, OpenAI, and SpaceX and use the transition period to verify model access, data policies, and workflow recovery. The episode is a reminder that AI-platform availability is shaped not only by model capability, but also by control, contract, and governance boundaries.
