Guides

OpenAI Pulls the Plug on Cursor: Your Own Key as Plan B

OpenAI will end direct access in Cursor by November 12 at the latest. An API key only preserves local chat and agent.

By Alec Chizhik September 3, 2026 5 min read

OpenAI Pulls the Plug on Cursor: Your Own Key as Plan B

OpenAI is serving Cursor its notice. The visible chat stays alive with your own key. The quiet Tab row loses its OpenAI model the moment this contract ends.

Key Takeaways

The deadline is a proposal. OpenAI sent SpaceX the termination notice on August 28, naming November 12 as the latest contract date. Cursor may cut ties earlier. The end date only takes effect once both sides have confirmed it.
Your own key only carries the desktop session. Local chat and the agent run through the OpenAI account. Tab, Auto, cloud agents, automations, the CLI and the Cursor API are left without the Cursor contract.
The upcoming OpenAI model Astra will not take this route. Future models are no longer supposed to arrive via Cursor. The Codex extension sits alongside and leaves the Cursor picker untouched.

Related:
SpaceX buys coding AI Cursor for 52 billion euros / Grok 4.5 in Cursor: blocked in the EU for now

The contract ends, the editor stays

Cursor looks the same as it did the day before. The model picker still lists the OpenAI models for as long as the contract runs. What has changed is the contract behind that list. OpenAI has informed SpaceX that it will let the supply contract for models in Cursor run out. November 12, 2026 is the latest date under the clause. Future models, Astra by name, are not supposed to take this route.

The reasoning sits in the company statement, not in a court ruling. OpenAI writes that it cannot rely on SpaceX using the technology within the terms of service. As evidence, OpenAI cites the contract breach after the Twitter acquisition and a sworn statement by Elon Musk from this year claiming xAI violated OpenAI’s rules. X and xAI now belong to the SpaceX group. The Cursor contract gives OpenAI a short window to terminate after a change of ownership. SpaceX took over Anysphere on August 14. The window is open. OpenAI is using it.

November 12 remains a proposal. Cursor may cut things off earlier. The official end arrives only once both companies have confirmed a date. Until then, direct access keeps running. Anyone who treats it as a given is planning around a contract that one side has already terminated.

Your own key opens only the local door

OpenAI describes three remaining routes: your own key, a gateway, and the Codex extension. The first is a personal API key in the Cursor settings under Models. Requests from local chat and the agent then run through the OpenAI account and its billing. A ChatGPT subscription does not cover this key. Anyone who already holds the same corporate access via Azure or Bedrock can attach a compatible gateway or an OpenAI-compatible base URL in the same place.

Key and gateway apply to supported local chat and agent requests in the desktop app. The quiet Tab row, Auto and the cloud layer stay on the outside. Anyone who uses the editor as invisible completion is relying on exactly the layer the key does not carry.

This shifts the bill. The switch alone is not enough. Until now, OpenAI was included in the Cursor subscription. After the cutoff, usage lands on the API invoice as soon as someone sets the key. In the services the key cannot reach, usage no longer exists at all. Before November, an inventory is worthwhile: which parts of your day rest on Tab or cloud agents.

Codex sits next to the model selector

The third workaround bypasses the selector. The Codex extension runs in Cursor with a ChatGPT subscription or API key. It doesn’t depend on whether OpenAI models appear in Cursor’s list. If you want Codex, you get Codex. If you want to keep the Cursor agent set to GPT, this doesn’t bring that back.

Tab and cloud agents need a different bus

The workable decision is therefore threefold. If you only need local chat and agent on OpenAI, set up the key or the gateway and watch until November whether Cursor honors the agreement. If you’ve put Tab or cloud agents on OpenAI, you need a different model in Cursor. If you want to leave the editor because the model bus has become a boardroom matter, plan the move now – not on November 11.

Cursor CEO Michael Truell told CNBC that OpenAI models account for roughly five percent of user traffic, and that talks with OpenAI are ongoing. Anthropic compute chief Tom Brown wrote after the announcement that Cursor remains a trusted partner and that compute capacity for Claude in Cursor would be increased. Neither of these changes the agreement. At most, it changes how full the selector will still look after the cutoff. The editor stays. Truell recently described the OpenAI platform as neutral infrastructure for his own business. OpenAI is now withdrawing exactly that neutrality.

Frequently Asked Questions

What is Cursor?

Cursor is an AI-powered development tool by Anysphere, Inc. The editor combines code completion and model selection in a single window. Since August 14, 2026, Anysphere has been part of SpaceX.

Is November 12 a fixed end date?

No. OpenAI names November 12, 2026 as the proposed, latest deadline from the agreement. Cursor can cut things off earlier. According to the help page, the official end comes once both sides have confirmed it.

Which Cursor features does a dedicated OpenAI key cover?

Local chat and agent in the desktop app. Tab, Auto, cloud agents, background agents, automations, the Cursor CLI, and the Cursor API including its SDK remain outside.

Does a ChatGPT subscription pay for the API key?

No. Usage via the key is billed through the OpenAI API account. A ChatGPT subscription does not include this usage.

Does the Codex extension replace the Cursor agent?

No. The extension runs alongside it and leaves Cursor’s model selector untouched. Chat, agent, Tab, Auto, and cloud agents keep their current model.