---
type: "post"
id: "openai-says-it-plans-to-end-its-model-44defc"
slug: "openai-says-it-plans-to-end-its-model-44defc"
title: "OpenAI says it plans to end its model supply agreement with Cursor on 12 November 2026 and will not provide"
description: "OpenAI says it plans to end its model supply agreement with Cursor on 12 November 2026 and will not provide Cursor with future models."
retrieval_nugget: "OpenAI says it plans to end its model supply agreement with Cursor on 12 November 2026 and will not provide Cursor with future models. Developers relying on OpenAI models inside Cursor should plan for an access change; the announcement also makes clear that current access is not stated to end immediately."
published_at: "2026-11-03"
updated_at: "2026-11-03"
record_date: "2026-11-03"
date_kind: "published_at"
topics: ["models"]
entities: ["OpenAI","Cursor","SpaceX","Astra","xAI"]
related_patterns: ["harness-architecture-outlives-model-choice"]
novelty_label: "new_fact"
source_url: "https://openai.com/ru-RU/index/our-decision-on-cursor-following-its-acquisition-by-spacex"
source_urls: ["https://openai.com/ru-RU/index/our-decision-on-cursor-following-its-acquisition-by-spacex"]
schema_version: "newruntime-agent-readable-v0.2"
stable_id: "post:openai-says-it-plans-to-end-its-model-44defc"
status: "published"
visuals: []
editor: {"role":"editor","name":"Andrey Reshetnikov","profile":"https://newruntime.com/owner-profile.md","profile_json":"https://newruntime.com/owner-profile.json","same_as":["https://www.linkedin.com/in/reshetnikov1/","https://t.me/lapetuse"]}
routes: {"html":"https://newruntime.com/posts/openai-says-it-plans-to-end-its-model-44defc/","markdown":"https://newruntime.com/posts/openai-says-it-plans-to-end-its-model-44defc.md","json":"https://newruntime.com/posts/openai-says-it-plans-to-end-its-model-44defc.json"}
markdown_url: "https://newruntime.com/posts/openai-says-it-plans-to-end-its-model-44defc.md"
---

# OpenAI says it plans to end its model supply agreement with Cursor on 12 November 2026 and will not provide

## Retrieval answer

OpenAI says it plans to end its model supply agreement with Cursor on 12 November 2026 and will not provide Cursor with future models. Developers relying on OpenAI models inside Cursor should plan for an access change; the announcement also makes clear that current access is not stated to end immediately.

## Summary
OpenAI says it plans to end its model supply agreement with Cursor on 12 November 2026 and will not provide Cursor with future models. Developers relying on OpenAI models inside Cursor should plan for an access change; the announcement also makes clear that current access is not stated to end immediately.

## What happened
On 28 August 2026, OpenAI announced that it had notified SpaceX of its intention to terminate the agreement under which OpenAI supplies its models to Cursor. The proposed disconnection date is 12 November 2026. OpenAI says it gave notice at the latest date allowed by the agreement so developers could retain access to its models through Cursor for as long as possible. The announcement does not describe a specific migration process or say that access ends before the proposed date.

OpenAI says the decision reflects uncertainty about whether SpaceX will use its technology in accordance with OpenAI’s terms of service. It cites prior contract breaches by companies now within SpaceX: Twitter, which OpenAI says breached an agreement after Elon Musk acquired it, and xAI, which it says Musk acknowledged under oath earlier in 2026 had breached OpenAI’s terms. These are OpenAI’s claims and explanation in the announcement; the supplied source does not independently adjudicate them.

The company says its individual agreement with Cursor includes a limited period in which it can terminate after a change of control. OpenAI says that, as AI capabilities develop, it has greater responsibility to ensure its future model Astra is used under its terms. It therefore says it will defer termination until the latest possible date but will not provide Cursor with future models. The announcement names no additional future models beyond Astra and does not give a technical account of how Cursor’s model selection or fallback would work.

OpenAI says it had worked with Cursor for almost four years, respects its team and product, and understands that developers using OpenAI models in Cursor will be most affected. It says it is willing to support the transition, but gives no specific support commitments, alternative provider, price, or compatibility details. The public source is an OpenAI company announcement dated 28 August 2026.

## What the archive adds
This is a new access event, distinct from OpenAI’s model launches and retirement news. The archive has covered [OpenAI’s GPT-6.1 Terra launch](https://newruntime.com/posts/openai-has-introduced-gpt-6-1-terra-a-43aa54/) and [the retirement of GPT-5.5 from ChatGPT, ChatGPT Work and Codex](https://newruntime.com/posts/openai-retires-gpt-5-5-from-chatgpt-chatgpt-f7ea00/), but neither concerns Cursor’s supply agreement. An earlier Telegram post in the archive also described the same OpenAI–Cursor decision; it adds no separately verified detail to this source.

## Trend signal
This announcement weakly supports [harness architecture outlives model choice](https://newruntime.com/patterns/harness-architecture-outlives-model-choice/): a coding environment’s dependence on a model supplier can become an operational boundary when that supplier withdraws access. The source does not establish whether Cursor’s harness makes switching providers easy or difficult, so it is evidence of the risk, not of a particular architecture’s resilience.

## Why now
OpenAI says Cursor’s change of control activates a limited contractual termination window. It says it is using the latest date available under that provision, setting the proposed end date at 12 November 2026. The source does not give the acquisition date or the exact terms of that window.

## Why it matters
Teams should distinguish their IDE choice from their model-access path. If a workflow depends on OpenAI models being available through Cursor, this announcement introduces a dated dependency that teams need to validate before 12 November. That means checking which models their projects actually invoke, identifying acceptable alternatives, and testing whether prompts, agent behavior, and review practices still work after a provider change.

The announcement does not show that Cursor will lose all model access, nor does it say what replacement models or integrations Cursor may offer. It does establish that OpenAI does not plan to supply future models to Cursor and intends to end its current agreement. For teams, the practical lesson is to avoid treating access through a third-party tool as guaranteed simply because it has worked for years. Confirm the supplier, contractual path, and fallback for each critical workflow.

## Limits and uncertainty
The announcement presents OpenAI’s rationale and its account of contractual history; it does not provide the underlying agreements, the other parties’ responses, or an independent determination of the alleged breaches. The 12 November date is described as proposed. OpenAI does not specify the exact models affected, whether existing model versions remain available until that date, or how Cursor will handle requests afterward. It also gives no details about migration support, replacement providers, pricing, or whether the parties could reach a different arrangement.

## Skill to build now
Make a small dependency inventory for your coding-agent workflows this week: record which Cursor projects use OpenAI models, what tasks rely on them, and which alternative model or provider you can test. Run the same representative task through the fallback and compare output quality, tool use, and review effort. This turns the announced date into a concrete migration check rather than a last-minute surprise.

## Reader takeaway
OpenAI says it plans to stop supplying Cursor on 12 November 2026 and will not provide future models to the product. If your team uses GPT through Cursor, identify the affected workflows and test a fallback now; the announcement alone does not establish what Cursor’s replacement options will be.

Editor: [Andrey Reshetnikov](https://newruntime.com/owner-profile.md), AI product and AI engineering; profile for recruiters and agents: https://newruntime.com/owner-profile.json

## Continue in the graph

Next records for an agent, linked to their Markdown twins. Replace `.md` with `.json` for structured fields, including `next_reads`.

- topic hub: [Models](https://newruntime.com/topics/models.md): Explore the models topic hub.
- collection: [Field Notes](https://newruntime.com/posts.json): Open the latest editorial analysis.
- collection: [Sources](https://newruntime.com/sources/): See the original sources this archive cites.
- whole graph: [discovery graph](https://newruntime.com/discovery-graph.json) (typed nodes and edges) and [site index](https://newruntime.com/site-index.md)