• 4 min read
OpenAI plans to end its direct Cursor agreement after SpaceX’s acquisition, but users can switch to API keys, Codex, or another model provider.
Image: Tom's Guide OpenAI plans to end its direct model-access agreement with Cursor on November 12, 2026, following SpaceX’s acquisition of the coding platform. The date is proposed rather than final: Cursor could terminate access earlier, and the timing could still change.
Existing OpenAI models should continue working inside Cursor for now. If the deal ends as proposed, new OpenAI models will not be added to Cursor under the existing agreement. OpenAI has documented the transition and workarounds in its official Cursor access guidance.
The dispute is tied to a change-of-control provision in OpenAI’s contract with Cursor. SpaceX’s acquisition changed the ownership relationship, putting Cursor’s continued access to models from a company that competes with Elon Musk’s AI businesses under review.
Recommended reading
OpenAI’s Python SDK switches its HTTP layer to HTTPX2
Tomas Berg • • 6 min read
Three ways Cursor users can keep using OpenAI models #
The practical effect depends on which Cursor features a developer uses. There isn’t one replacement that preserves every part of Cursor’s current OpenAI integration.
| Route | What it provides | Main limitation or cost |
|---|---|---|
| Personal OpenAI API key | OpenAI models for supported Chat and Agent requests | Separate API billing; no access to several Cursor-native features |
| OpenAI Codex IDE extension | OpenAI’s coding agent inside Cursor’s VS Code-based editor | Separates the coding agent from Cursor’s native AI integration |
| Cursor’s other models | Continued use of Cursor with Anthropic Claude, Cursor models, and other providers | Developers must switch away from OpenAI models |
The most direct workaround is to add a personal OpenAI API key in Cursor’s settings. That sends supported Chat and Agent requests to OpenAI instead of routing them through Cursor’s existing agreement.
The API-key option does not restore OpenAI throughout Cursor. OpenAI says personal keys don’t cover Cursor Tab and autocomplete, Auto, Cloud or Background Agents, Automations, Cursor CLI, or Cursor’s API and SDK. Those restrictions exclude several automated and editor-integrated workflows.
The billing model also changes. A ChatGPT Plus or Pro subscription does not include OpenAI API credits, so a developer who moves from Cursor’s bundled access to a personal key will pay separately for API consumption. The supplied material does not specify API rates or forecast a typical monthly bill.
Codex keeps OpenAI in the editor, not necessarily in Cursor’s stack #
Developers who mainly want an OpenAI coding agent can install OpenAI’s Codex IDE extension. Cursor is based on VS Code, so compatible extensions can be installed inside the editor. Cursor remains the code editor while Codex provides a separate OpenAI coding experience.
The extension is not described as a way to restore Cursor Tab, autocomplete, Background Agents, Automations, or Cursor’s API and SDK. It is an alternative OpenAI interface inside the same editor, rather than a continuation of the existing integration.
For developers who specifically want access to OpenAI’s newest coding models and agents, the Codex extension may be a practical route. It also means managing two product layers: Cursor for the editing environment and OpenAI for the coding agent.
Switching providers may affect most users the least #
The third option is to stay with Cursor and select another model. Cursor supports Anthropic’s Claude, its own models, and models from other providers, so developers who don’t depend on GPT may not need to change anything when the agreement ends.
Cursor co-founder Michael Truell has said OpenAI represents about 5% of Cursor’s model traffic. That figure suggests the platform’s overall usage is not heavily dependent on OpenAI, although it doesn’t show how many individual developers rely on GPT or how much revenue is tied to those requests. It also doesn’t establish whether the 5% figure covers every Cursor product and workflow.
The acquisition creates a risk for Cursor’s multi-model pitch. OpenAI is the first major provider identified as changing its relationship with Cursor after the SpaceX deal. If other providers impose similar restrictions, the platform could lose some of the model choice that has been central to its product. If they do not, users may be able to switch with limited disruption.
For US developers, there is no stated immediate shutdown and no announced change to Cursor’s price in the supplied material. The confirmed near-term action is the proposed November 12, 2026 end date. It remains unclear whether Cursor can preserve access to future OpenAI models through a new agreement or must rely on user-managed API access and a separate Codex extension.
Frequently asked questions #
Can I still use OpenAI models in Cursor after November 12, 2026?+ #
OpenAI has proposed ending its direct agreement with Cursor on November 12, 2026. Users may continue with supported requests through a personal OpenAI API key or use the Codex IDE extension.
Does ChatGPT Plus include OpenAI API credits for Cursor?+ #
No. ChatGPT Plus and Pro subscriptions do not include OpenAI API credits, so API-key users pay separately for API usage.
Which Cursor features will not work with my OpenAI API key?+ #
OpenAI says personal API keys won’t work with Cursor Tab and autocomplete, Auto, Cloud or Background Agents, Automations, Cursor CLI, or Cursor’s API and SDK.
Why is OpenAI ending its Cursor agreement?+ #
The change follows SpaceX’s acquisition of Cursor, which triggered a change-of-control provision in OpenAI’s agreement with the company.
Tomas Berg Computing Editor
Tomas lives in the terminal. He covers chips, laptops, and operating systems with a focus on performance and efficiency. He reads kernel changelogs the way other people read fiction, and he's always on the hunt for the perfect mechanical keyboard switch. If it processes data, Tomas has an opinion on it.