OpenAI's Cursor Cutoff Date Arrives Today — But Neither Side Says the Models Went Dark

Today, 12 November, is the date OpenAI named for ending Cursor's direct access to its models — but as of last night, neither company had said whether the models actually went dark. The date comes from OpenAI's own blog post of 28 August 2026, and the word OpenAI used in it was "proposal", not decision. That distinction is the whole story: the cutoff date has arrived, and the cutoff itself is still unconfirmed.

On 28 August, OpenAI published a post titled "Our decision on Cursor following its acquisition by SpaceX", writing: "Under our proposal, Cursor's direct access to our models would end on November 12." Since then, both sides have kept talking. Cursor chief executive Michael Truell said OpenAI models account for about 5% of Cursor's user traffic and that the companies were speaking to resolve the situation. Neither side had said, as of 11 November, whether the models were still live — and no source found on 12 November confirms they were actually removed today.

What the proposal actually covers

The proposal, as OpenAI described it, covers Cursor's direct, built-in access to OpenAI models — the models that appear in Cursor's own picker, supplied through OpenAI's partnership with the company. If it takes effect, those built-in models would stop working inside Cursor.

What it does not cover matters just as much. Developers using their own OpenAI API keys inside Cursor would not be affected — that is a separate arrangement, not Cursor's built-in access — and OpenAI's own IDE extensions are unaffected. Even in the worst case, the cutoff is not a blanket ban on OpenAI models in Cursor; it is the end of the built-in, ready-to-use supply.

Exactly which models sit inside that built-in supply is something this article will not list as fact. Sources disagree on the model names involved, and naming them would create a false sense of precision. What is confirmed is the shape of the proposal: direct access ends on 12 November, under the proposal OpenAI published.

A woman developer with glasses works late at night on a laptop showing code, a coffee cup and headphones on the desk (AI-generated illustration, credit: INORYVA)
A woman developer with glasses works late at night on a laptop showing code, a coffee cup and headphones on the desk (AI-generated illustration, credit: INORYVA)


Why OpenAI proposed it: the SpaceX deal

The trigger is corporate, not technical. In June 2026, SpaceX agreed to buy Anysphere, the company behind Cursor, in a $60 billion all-stock deal. OpenAI's problem is who would then control the company using its models.

OpenAI put it bluntly in its August post. The company said it "cannot be confident that SpaceX will use our technology within our terms of service, based on our experience with Elon Musk's companies violating contracts." That is an unusually direct statement for a company blog post, and it is the stated reason for the proposed cutoff: not a dispute over price or performance, but a lack of confidence that the new owner would honour OpenAI's terms.

OpenAI also made clear the cutoff would extend forward, not just backward. The company said it will not supply future models — including the upcoming Astra — to Cursor. For Cursor, that would mean losing access not only to today's models but to whatever OpenAI releases next, for as long as the dispute stands.

Why 5% matters more than it sounds

Truell's figure — OpenAI models are about 5% of Cursor's user traffic — sounds small, and it is worth asking why a 5% share would matter. The answer is that traffic share is not the same as importance. A model can be a small share of total usage and still be the one developers reach for in specific situations: a tricky debugging session, a particular language, or a workflow built around one model's strengths.

It also matters because Cursor's appeal is choice: developers pick the best model for each job inside one tool. Losing a major provider narrows that choice, and with no future models — including Astra — the gap would widen over time rather than stay at 5%.

The 5% figure also explains why the talks have dragged on: for Cursor, losing the built-in models is painful but not fatal; for OpenAI, the leverage is real but limited. Both sides have reasons to keep negotiating.

What to watch for now

Three things will settle this story. The first is the simplest: whether Cursor users open the editor today and find OpenAI models still in the picker, or gone. That is a fact either company could confirm in a sentence, and neither has — which is why this article reports the date as proposed, not as done.

The second is whether the talks Truell described produce a deal. A commercial agreement, a revised set of terms, or a time-limited extension would all change the picture, and any of them would be announced by one side or the other. Until then, the 28 August proposal is the last formal word from OpenAI, and the last public word from Cursor is that talks continue.

The third is Astra. OpenAI has said it will not supply the upcoming model to Cursor, and that matters more than today's date in the long run: if Astra becomes a model developers want, its absence from Cursor would be felt more keenly than the loss of today's models. For context, see our flagship AI model  comparison.

Close-up of a laptop screen showing a code editor beside an AI coding assistant panel with a model selection menu (AI-generated illustration, credit: INORYVA)
Close-up of a laptop screen showing a code editor beside an AI coding assistant panel with a model selection menu (AI-generated illustration, credit: INORYVA)


The wider pattern: AI tools are getting political

This dispute is not really about one code editor. It is about what happens when AI models become infrastructure, and the companies that build them start choosing who gets to build on top of them. OpenAI's reasoning is explicitly about trust in a counterparty, not about Cursor's product. That is a new kind of gatekeeping: access to a model decided by the politics of an acquisition, not by a price list.

Developers have seen platforms change API terms before, but the stakes are higher when the tool is a frontier model inside a daily workflow. The practical lesson: if your workflow depends on one provider's built-in access, you are exposed to decisions you do not control. Keep your own API keys, and keep your tooling portable.

It is also a reminder that the AI coding market is consolidating around a small number of model providers and a small number of editors. OpenAI itself is building agent tooling, as covered in our piece on the OpenAI Decisions API, and Anthropic is building its own collaborative coding tools, including Claude Duet Anthropic. Every provider is now both a model supplier and a competitor to the tools that use its models.

Two colleagues discuss a laptop in a glass-walled office, a whiteboard behind them showing a system diagram (AI-generated illustration, credit: INORYVA)
Two colleagues discuss a laptop in a glass-walled office, a whiteboard behind them showing a system diagram (AI-generated illustration, credit: INORYVA)


What Cursor users should do today

First, check the picker. If OpenAI models are still listed in Cursor, nothing has changed for you yet — the proposal has not taken effect, whatever the date says. If they are gone, the fallback is your own OpenAI API key, which the proposal does not touch, or one of the other models in Cursor's picker.

Second, do not assume the situation is final. The talks were ongoing as of 11 November, and a proposal is not a cutoff until it is enforced.

Third, watch for an official word rather than a rumour. A changelog entry, a status page update, or a post from either company will settle it. Until one appears, any claim that the models "went dark today" is speculation.

Key Takeaways

  • 12 November is the date in OpenAI's 28 August 2026 proposal for ending Cursor's direct access to its models — it is a proposed date, not a confirmed cutoff.
  • As of 11 November, both sides were still talking, and neither had said whether the models were still live. No source found on 12 November confirms the models actually went dark.
  • The proposal covers Cursor's built-in, direct OpenAI models. It does not end developers' own OpenAI API keys in Cursor, or OpenAI's own IDE extensions.
  • The trigger is SpaceX's agreed $60 billion all-stock purchase of Anysphere (Cursor) in June 2026; OpenAI says it cannot be confident SpaceX will use its technology within its terms of service.
  • OpenAI also says it will not supply future models, including the upcoming Astra, to Cursor.
  • Cursor CEO Michael Truell said OpenAI models are about 5% of Cursor's user traffic — small, but the loss of choice and of future models matters more than the share.

Conclusion

The date has arrived, but the cutoff has not been confirmed. OpenAI proposed on 28 August that Cursor's direct access to its models would end on 12 November, citing the SpaceX acquisition and a lack of confidence in the new owner's respect for its terms. Yet as of 11 November the two companies were still talking, the models' live status was unconfirmed, and no source on 12 November has shown them gone. For Cursor users, the honest position is to check the picker, keep a fallback ready, and wait for an official word — because today is the proposed date, and a proposal is not a shutdown until somebody enforces it.

Sources

Comments

Post a Comment