If you use OpenAI models in Cursor, the clock is nearly out. OpenAI plans to end its model access to the editor on November 12, 2026, after SpaceX bought Cursor. Cursor itself keeps running, but anything you have pinned to a GPT model will need a new home.
Here’s what stops working, what you can still do, and how to switch without wrecking your workflow.
- Cutoff date: November 12, 2026 (OpenAI’s proposed date; Cursor could end access earlier).
- Who’s affected: anyone using OpenAI models as their default, per-feature, or agent model in Cursor.
- Not affected: Cursor’s own models and other providers such as Anthropic’s Claude.
- New models: OpenAI won’t supply future models, including GPT-6 Astra, to Cursor.
The short version is that your editor stays, and one model supplier leaves.
Why OpenAI is pulling out of Cursor
SpaceX completed its acquisition of Cursor in August. That triggered a change-of-control clause in OpenAI’s contract, which gave OpenAI a limited window to cancel. OpenAI announced on August 28 that it would wind the deal down, saying it couldn’t be confident SpaceX would use its technology within its terms of service.
The cutoff has been widely reported, including by Tom’s Guide and CNBC. Treat November 12 as the planned date, not a guarantee. Tom’s Guide notes the timing could shift, and Cursor could end access sooner.
What happens to OpenAI models in Cursor on November 12
Existing OpenAI models keep working in Cursor until the cutoff. After that, they won’t be served through Cursor’s own subscription. Here’s how that plays out by situation.
| Your setup | What happens after Nov 12 | What to do |
|---|---|---|
| GPT model as your default | Stops working through Cursor | Pick a replacement default model now |
| Agent or Chat pinned to OpenAI | Requests fail or need rerouting | Switch model, or use your own API key |
| Prompts and rules tuned for GPT | May give different results on another model | Retest on real tasks before the deadline |
| Claude or Cursor’s own models | No change | Nothing required |
The catch is output quality. Rules and prompts you tuned for one model often behave differently on another, so test before you’re forced to.
Three ways to keep going
Per Tom’s Guide, you have three realistic options.
| Option | How it works | Limits |
|---|---|---|
| Bring your own API key | Add your OpenAI key in Cursor settings to route Chat and Agent requests directly to OpenAI | Doesn’t cover Tab autocomplete, Auto, Cloud or Background Agents, CLI, or the Cursor API; API usage is billed separately |
| OpenAI’s Codex extension | Install the Codex IDE extension inside Cursor, since it’s built on VS Code | Separate tool and separate workflow from Cursor’s agents |
| Switch models in Cursor | Use Claude or Cursor’s own models | Your prompts may need retuning |
A ChatGPT Plus or Pro subscription doesn’t include API credits, so the API-key route means a second bill. If you’re curious about OpenAI’s Codex direction, our look at the OpenAI Pierre acquisition and Codex covers it.
How much will you actually notice?
Probably less than the headlines suggest. Cursor co-founder Michael Truell said OpenAI models account for only about 5% of Cursor’s model traffic, as reported by Tom’s Guide. If you already use Claude or Cursor’s own models, you may notice nothing.
If GPT is your daily driver, though, it’s a real change. This is also a reminder that your AI coding setup depends on contracts you can’t see. Cursor’s newer features, like those in our post on Cursor Build Live Apps, could be affected by model availability too.
Why this matters beyond Cursor
AI coding tools are built on top of model deals. When a company is acquired, those deals can change overnight, as this one shows.
That’s a good reason to avoid tying every habit to one model. Keep your rules files model-neutral where you can, and test a second model every few weeks so a switch never feels like an emergency. It also helps to know which of your tools can take your own API key and which can’t.
A simple pre-deadline checklist
You’ve got a few days, so do these in order. Each takes only a few minutes.
- Open Cursor settings and note which model is your default and which features use OpenAI models.
- Run a real task from your current project on a non-OpenAI model and compare the result.
- Update any rules or prompt files that mention a specific model.
- Check pricing for the model you switch to, since usage billing differs by model.
Doing this now means you won’t find out on deadline day that your agent workflow quietly broke.
Frequently Asked Questions
Is Cursor shutting down?
No. Only OpenAI’s supply of models to Cursor is ending. Cursor continues with other providers and its own models.
Will my OpenAI API key still work in Cursor?
Tom’s Guide says bring-your-own-key can route Chat and Agent requests to OpenAI, but not every feature. OpenAI’s statement doesn’t spell this out, so check Cursor’s docs and announcements before relying on it.
Will GPT-6 Astra come to Cursor?
Not through the current agreement. OpenAI said it won’t make new models available in Cursor.
Can the date change?
Yes. November 12 is OpenAI’s proposed date, and Cursor could end access earlier.
My take: don’t wait for November 12. Switch your default model this week, keep a spare API key for the odd GPT task, and treat any single model supplier as temporary. Cursor is still a good editor, but your workflow should survive a supplier change.
Leave a Reply