OpenAI sets a shutoff date for Cursor's access to its models
OpenAI notified SpaceX on August 28 that it intends to wind down the contract that puts its models inside Cursor, and it proposed November 12, 2026 as the shutoff date. The stated reason is that OpenAI cannot be confident SpaceX will stay inside its terms of service. Cursor is also cut out of Astra, the model OpenAI says is coming. If you write code in Cursor against an OpenAI model, that part of your setup now has an expiry date.
Source
Our decision on Cursor following its acquisition by SpaceXOpenAI News · Original published August 28, 2026
OpenAI has put a date on Cursor. In a note published on August 28, the company said it notified SpaceX that it intends to wind down the contract supplying OpenAI models to the editor, with a proposed shutoff on November 12, 2026. SpaceX now owns Cursor, and that change of control is what opened the cancellation window OpenAI is using.
What OpenAI said
The note is short and unusually direct about motive. OpenAI writes that it cannot be confident SpaceX will use its technology within its terms of service, and it grounds that in two earlier events. After Musk acquired Twitter, now part of SpaceX, the company broke the terms of an OpenAI contract. Under oath earlier this year, Musk admitted that xAI, also now part of SpaceX, had violated OpenAI's terms of service.
OpenAI also says it is giving the maximum notice its contract allows, so developers keep access for as long as possible. That is why the shutoff lands in November rather than next week.
Why a change of control opens the door
Large partners do not run on the public terms of service. OpenAI says it relies on custom contracts with a partner the size of SpaceX, both to enforce compliance and to keep the integration safe at scale. Its agreement with Cursor carries a clause giving OpenAI a limited window to cancel after a change of control, and that window is what is being used now.
There is a forward-looking reason too. OpenAI says its coming model, Astra, brings a new level of accountability for how it is used, and the company has decided not to supply future models to Cursor at all. The wind-down and the withholding of Astra are two decisions announced together, not one.
What it means if you build in Cursor
Nothing breaks today. OpenAI models keep working in Cursor until the proposed shutoff, and OpenAI says it worked with Cursor for nearly four years and wants to support developers through the transition. What changes is planning: any workflow, prompt library or evaluation set tuned to a specific OpenAI model inside Cursor now has an end date attached.
The useful check is how much of your setup depends on one vendor's model rather than on the editor itself. Cursor still offers models from other providers, and work that moves cleanly between models survives November 12 untouched. Work tuned to one model does not.
„we cannot be confident that SpaceX will use our technology“
Once a week, in your inbox
The whole week's news, gathered into one email. No ads, no passing your address on, one-click unsubscribe.
The address is used only for this roundup. It is not sold and not passed to anyone.
Related
Claude Code 2.1.321 stops MCP sign-in from sending refresh tokens to another host after a redirect
The most serious fix in the release concerns MCP servers that require an OAuth sign-in. Three more fixes cover cases where a shell command or a file write got past a permission check. Claude Fable 5.2 also becomes the default Fable model.
Anthropicverified
OpenClaw 2026.11.2 stops project settings from adding programs to the agent's PATH
OpenClaw's latest patch release adds no features and fixes a set of security problems. The most serious one let a settings file inside a project add programs from that project to the list of directories where the system looks for commands. Two of the fixes change existing behavior, so some setups need to be adjusted.
OpenClawverified

GitHub Copilot now runs in JetBrains Air, and its cloud tasks use a Copilot plan instead of JetBrains credits
Copilot can now be picked as an agent in Air for local and cloud coding work, on an existing subscription. Air administrators can switch it off, but they cannot cap its spending in Air or see its usage in Air's analytics.
GitHubverified
