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“
Related
OpenClaw 2026.9.4 can undo a failed update, and its ready cloud workers bill until deleted
OpenClaw published version 2026.9.4 on September 11, 2026. A failed update can now restore the previous package, but only where schema and configuration checks show the rollback is safe, and database migrations still require a verified backup taken before the upgrade. The same release adds prepared cloud workers that keep costing provider money until they are deleted, with a default reserve of one per project or profile and a ceiling of four across the Gateway. Plugins move into a single workspace, and a host can now lock configuration through an environment variable.
OpenClawverified
GitHub retired MAI-Code-1-Flash across Copilot the same day it announced the change
GitHub deprecated MAI-Code-1-Flash on September 10, 2026, and the changelog entry carries that same date for both the announcement and the retirement. The model is gone from Copilot Chat, inline edits, ask mode, agent mode, and code completions. GitHub names MAI-Code-1.1-Flash as the suggested alternative and asks teams to update anything that calls the old model by name. On Copilot Enterprise the alternative does not show up until an administrator enables it in the model policies.
GitHub Changelogverified
Claude Code 2.1.268 closes several ways a deny rule failed to apply
The release published on September 10, 2026 is mostly a permissions release. Deny and ask rules did not apply to symlinked directories when a path was spelled by its real location, and a deny rule on a file could be stepped over by putting an unparseable command on the same line. Two separate fixes stop secrets from being printed into plugin and MCP output. The same build also repairs third-party endpoints, which had been failing every turn with HTTP 400 since 2.1.265.
Claude Code Releases (GitHub)verified

