ToolNavs Find Useful AI Tools
Submit Sign in
Back to AI information
OpenAI Models Exit Cursor Today: Nov 12 Cutoff Arrives — What Developers Should Switch To

OpenAI Models Exit Cursor Today: Nov 12 Cutoff Arrives — What Developers Should Switch To

AI information • Admin • • 23 views

On November 12, the transition period for OpenAI's model supply to Cursor expires today. In an announcement published on August 28, OpenAI said it intends to stop supplying models to Cursor after SpaceX completed its acquisition of Cursor's parent company, Anysphere, and set November 12 as the proposed cutoff date. For people who write code in Cursor every day, this is not distant business news — it is a change to their tools that lands today.

The trigger was a change of ownership. SpaceX announced in June that it would acquire Anysphere in a $60 billion all-stock deal, which closed on August 14. OpenAI then invoked the change-of-control clause in its contract, notified SpaceX that it would wind down the model-supply agreement, and gave the maximum notice the contract allows. OpenAI's stated reason was blunt: it cannot be confident that SpaceX will use its technology within its terms of service, citing Musk-owned companies' past contract violations — including Musk's admission under oath earlier this year that xAI had violated OpenAI's terms of service. OpenAI also made clear that Astra, the new model it is developing, will not be provided to Cursor.

Who is affected, and who is not

Directly affected are users who pick GPT models in Cursor's model picker. Cursor CEO Michael Truell responded in August that OpenAI models account for about 5% of Cursor's traffic, that the two sides are still talking, and that the date is only a proposal rather than a final confirmation — Cursor could also end supply earlier. Much more is unaffected: Anthropic's Claude, Google's Gemini, xAI's Grok and Cursor's own Composer models will keep working; users can still call GPT models in Cursor with their own OpenAI API key; and OpenAI's coding extensions that run inside editors will continue to be supported.

What to do from today

The safest move is to check right now which model is your default in Cursor, and move any workflows, prompt presets and agent setups that depend on GPT models to Claude or Gemini in advance — or switch to the bring-your-own-key route. Cursor itself has not stood still either: its team feature Cursor Projects is pushing ahead with multi-person agent programming. The longer lesson is model portability: when one provider can pull its models over a change of ownership, a developer's toolchain should not rest on a single model. Whether the cutoff actually lands today still depends on the date the two sides finally confirm.

Recommended Tools

More