update · TowCue Editorial Team
OpenAI to end Cursor model access November 12 after SpaceX acquisition
OpenAI will wind down its contract providing models to Cursor after SpaceX acquired Anysphere. Proposed shutoff: November 12, 2026. What developers need to know.
Quick answer
OpenAI announced 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. The decision follows SpaceX's acquisition of Cursor's parent company Anysphere (completed ~August 14, 2026). OpenAI cites inability to trust SpaceX (which now includes X and xAI) to comply with its terms of service, based on prior contract violations. OpenAI will not provide future models (including the upcoming Astra) to Cursor during the wind-down. Developers have ~76 days of transition; OpenAI published a companion Help Center article documenting three workaround paths: bring-your-own OpenAI API key, Codex IDE extension, and AI gateway providers.
What happened
Official source: OpenAI Blog — "Our decision on Cursor following its acquisition by SpaceX" (August 28, 2026)
Support doc: Using OpenAI models in Cursor (published August 29, 2026)
Timeline
| Date | Event |
|---|---|
| June 16, 2026 | SpaceX announces all-stock acquisition of Anysphere (Cursor maker), valued ~$60B |
| ~August 14–15, 2026 | Acquisition closes; Cursor folds into SpaceXAI alongside xAI and X |
| August 28, 2026 | OpenAI publishes decision; notifies SpaceX of intent to wind down contract; proposes November 12, 2026 shutoff |
| November 12, 2026 | Proposed date for direct OpenAI model access via Cursor to end |
Key facts from OpenAI's announcement
- Trigger: Change-of-control clause in the custom Cursor agreement activated by SpaceX's acquisition
- Notice period: Maximum allowed by contract (~76 days from notice to proposed shutoff)
- Future models: No future OpenAI models (including Astra) will be provided to Cursor during wind-down
- Current models: GPT-5.6 Luna, Sol, Terra remain available until shutoff
- Traffic impact: OpenAI models account for ~5% of Cursor user traffic (per Cursor CEO Michael Truell)
- Tone: OpenAI emphasizes respect for Cursor team ("nearly four years," "enormous respect") — the issue is the new parent company, not the product
Why OpenAI did this
OpenAI states it "cannot be confident that SpaceX will use our technology within our terms of service" based on:
- X (formerly Twitter): After Musk's acquisition, X broke OpenAI contract terms (NYT, April 2023)
- xAI: Musk admitted under oath (April 2026) that xAI distilled OpenAI outputs for training, violating OpenAI's terms (Forbes, April 2026)
- Astra accountability: As capabilities advance, OpenAI needs stricter control over where its frontier models (starting with Astra) are deployed
The custom Cursor agreement gave OpenAI a limited window to cancel after change of control — OpenAI chose to use it while maximizing notice.
What this means for developers
What stops on November 12 (proposed)
| Feature | After Nov 12 |
|---|---|
| OpenAI models via Cursor subscription (GPT-5.6 Luna/Sol/Terra) | Gone |
| Future OpenAI models (Astra, etc.) in Cursor | Never shipped |
| Auto model selection/routing to OpenAI | Gone |
| Cloud/Background Agents using OpenAI | Gone |
| Cursor CLI / API / SDK with OpenAI | Gone |
| Cursor-provided proprietary models | Unaffected (these are Cursor's own) |
What continues working
| Feature | Status |
|---|---|
| Cursor editor itself | ✅ Works |
| Composer (Cursor's own model) | ✅ Works |
| Anthropic (Claude) models in Cursor | ✅ Works |
| Google (Gemini) models in Cursor | ✅ Works |
| xAI (Grok) models in Cursor | ✅ Works (likely more investment) |
| Your repository, rules, settings | ✅ Yours |
| Codex IDE extension / CLI (OpenAI's own) | ✅ Works |
Three workaround paths (per OpenAI Help Center)
OpenAI's companion article "Using OpenAI models in Cursor" documents three options:
1. Bring your own OpenAI API key (BYOK)
- Scope: Local Chat and Agent features only
- Billing: Your OpenAI API account (separate from Cursor/ChatGPT subscription)
- Limitations: Does not work for:
- Cursor Tab and autocomplete
- Auto model selection and routing
- Cloud or Background Agents
- Automations
- Cursor CLI / Cursor API / SDK
- Cursor-provided or proprietary models
- Setup: Settings → Models → OpenAI API key → paste project-scoped key → verify
- Note: ChatGPT subscription does not include API usage; BYOK bills to your OpenAI API account
2. OpenAI Codex IDE extension / CLI
- Scope: Full OpenAI model access (including future models) in your IDE
- Billing: Your OpenAI API account or ChatGPT subscription (per Codex terms)
- Advantage: Direct from OpenAI; no intermediary restrictions
3. AI Gateway providers (OpenAI-compatible endpoints)
- Examples: Amazon Bedrock, Azure OpenAI, or self-hosted gateways
- Scope: Same limitations as BYOK — only covers local Chat/Agent
- Use case: Central routing, governance, multi-provider normalization
Critical nuances
"Proposed" shutoff date
OpenAI uses the word "proposed" for November 12 throughout. The Help Center clarifies:
"Cursor may choose to end access sooner. We will share the official termination date as soon as it is confirmed between both companies."
Treat November 12 as the latest plausible date, not a guarantee.
BYOK ≠ full replacement
Many developers assume BYOK restores full OpenAI access inside Cursor. It does not. The Help Center is explicit:
- BYOK covers only local Chat and Agent requests
- Tab, Auto, Cloud Agents, Automations, CLI, SDK, Cursor API — all excluded
- Reasoning models and GPT-5 class models not supported via BYOK in Cursor (per Cursor docs as of 2026-03-18)
Cursor CEO's response
Michael Truell (Cursor CEO) posted on X (August 29):
- OpenAI models = ~5% of Cursor user traffic
- "We're speaking with the OpenAI team to resolve this"
- "Cursor was one of the very first users of OpenAI... trusted their platform to be neutral infrastructure"
Negotiations are ongoing; the notice could be withdrawn or terms revised.
TowCue take
This is a governance decision dressed as a contract enforcement. The technical mechanism (change-of-control clause) is real, but the choice to exercise it — while explicitly withholding future models — signals OpenAI's intent to deny frontier-model access to any Musk-controlled distribution channel.
For most Cursor users (95%+): No immediate impact. Composer, Claude, Gemini, Grok continue.
For the ~5% using OpenAI models via Cursor subscription: You have a transition window. Prioritize:
- Audit automated workflows — CI, scripts, unattended agents using OpenAI via Cursor will fail silently on shutoff
- Evaluate BYOK viability — If your use case is Chat/Agent only and you accept metered billing, BYOK is a bridge
- Test Codex IDE extension — Most seamless path for OpenAI-first workflows; same models, direct relationship
- Monitor negotiations — Truell confirmed talks with OpenAI; the notice could change
For teams: This is a reminder that model supply chains have counterparty risk. The editor (Cursor) and the model provider (OpenAI) are now competing entities under rival ownership. Diversify your model dependencies — don't bind critical automation to a single provider's embedded access.
Verify the official termination date on or before November 12 via OpenAI's channels. Do not assume the proposed date is final.
Research sources
- OpenAI Blog — "Our decision on Cursor following its acquisition by SpaceX" (August 28, 2026)
- OpenAI Help Center — Using OpenAI models in Cursor (August 29, 2026)
- Cursor Docs — Bring your own API key (current)
- CNBC — OpenAI to end model access to Cursor after acquisition by SpaceX (August 30, 2026, secondary confirmation)
- NYT — Elon Musk's AI fight with OpenAI (April 2023, cited by OpenAI)
- Forbes — Musk admits xAI distilled OpenAI data (April 2026, cited by OpenAI)