OpenAI Is Ending Its Cursor Model Deal: What Developers Need to Know

Tech · AI Coding · Developer Tools

OpenAI says it will wind down its agreement to supply models to Cursor after SpaceX acquired Cursor's parent company. Existing OpenAI model access is planned to continue until November 12, 2026.

Published August 29, 2026

Open model architecture illustration used as a visual for this AI developer tools article
Quick answer: OpenAI notified SpaceX on August 28, 2026 that it intends to wind down its contract supplying OpenAI models to Cursor, with a proposed shutoff date of November 12, 2026. OpenAI says the decision followed SpaceX's acquisition of Cursor and concerns about contract and usage compliance. OpenAI also says it will not provide future models such as Astra to Cursor, while existing access can continue during the notice period.

What happened?

OpenAI announced on August 28 that it intends to end its model supply agreement with Cursor. The company gave November 12, 2026 as the proposed shutoff date and said it is giving the maximum notice allowed by its contract so developers have more time to transition.

The trigger is Cursor's change in ownership. Cursor's parent company, Anysphere, was acquired by SpaceX. OpenAI says its agreement with Cursor contains a change-of-control provision that gives it a limited window to cancel the deal after a change in ownership.

OpenAI says it is not ending the relationship because of Cursor's product or team. It says it has worked with Cursor for nearly four years and respects what the company built for developers. The concern is whether SpaceX will use OpenAI technology within OpenAI's terms.

The timeline

DateEvent
June 2026SpaceX announced an agreement to acquire Anysphere, Cursor's parent company, in a reported $60 billion all-stock transaction.
August 14, 2026SpaceX completed the acquisition, according to reporting cited by the Indian Express.
August 28, 2026OpenAI announced that it intends to wind down its Cursor model supply contract.
November 12, 2026Proposed date for existing OpenAI model access through Cursor to end.

The November date is about the existing supply relationship. OpenAI says future models will not be supplied to Cursor, so the platform should not expect new OpenAI model releases during the transition.

What changes for developers?

If you use Cursor with OpenAI models today, the immediate change is not an instant shutdown. OpenAI says developers can keep access until November 12, 2026 under the current arrangement.

After that date, developers will need to use other models available through Cursor or move part of their workflow to another coding tool or direct model provider. Cursor is designed as a multi-model coding environment, so the impact depends on how much of a user's workflow relies specifically on OpenAI models.

Indian Express reported that Cursor co-founder Michael Truell said OpenAI models account for about 5% of Cursor user traffic and that the teams are speaking to each other about the issue. That suggests the impact on the overall product may be smaller than the headline makes it sound, but individual developers who prefer OpenAI models could still need to change their setup.

What about future OpenAI models?

OpenAI says it will not provide future models to Cursor, specifically mentioning Astra in its announcement. So the issue is not only the November cutoff for current models. Cursor would also lose the ability to receive new OpenAI models through this agreement unless the companies reach a new arrangement.

For developers, that creates a simple planning question: should OpenAI remain a core part of your coding stack if the integration may stop receiving future models?

What Cursor says

Cursor co-founder Michael Truell said the company was disappointed by OpenAI's announcement and that the teams were talking to try to resolve the situation. Indian Express reported that Truell said OpenAI models account for about 5% of Cursor traffic.

That response matters because it shows the situation may not be completely settled. OpenAI has announced its intention to wind down the contract, but the November 12 date still leaves time for the companies to discuss a resolution.

Why this matters for AI coding tools

The deeper issue is the changing relationship between model providers and AI applications. A coding tool can start as neutral software that connects users to several model providers. But if the coding tool is acquired by a company with its own AI interests, model providers may begin to see it as a strategic competitor rather than a neutral distribution partner.

That can affect developer choice. A multi-model coding environment is valuable partly because users can switch models based on quality, price, privacy, speed, and task. Ownership changes can make those relationships more complicated.

The episode also shows why model access should not be treated as permanent infrastructure. AI developers need to think about provider concentration, contract changes, model retirement, pricing, and fallback models when they build long-term workflows.

For teams that are comparing AI tools, ToolboxKart's Content Freshness Checker can help identify pages that need review when fast-changing product facts become outdated.

What developers should do now

  • Check your model mix: identify which projects depend on OpenAI models inside Cursor.
  • Test alternatives: compare the other models available in your coding workflow before the cutoff.
  • Keep prompts portable: avoid building critical workflows around provider-specific behavior where possible.
  • Review privacy settings: understand how each model provider handles your code and data.
  • Watch the November deadline: treat November 12, 2026 as the current planning date.

Bottom line

OpenAI is planning to stop supplying models to Cursor on November 12, 2026 after SpaceX acquired Cursor's parent company. OpenAI says the decision is based on contract and compliance concerns, while Cursor says it is talking with OpenAI to try to resolve the issue.

For developers, the lesson is bigger than Cursor. AI coding tools are becoming strategic platforms, and ownership changes can affect which models developers can use. The safest approach is to keep your workflow flexible and have more than one strong model option.

Sources