OpenAI is pulling its models from Cursor on 12 November — a live vendor lock-in warning for anyone betting on one AI coding stack

OpenAI told Anysphere on 28 August that it will end Cursor's access to OpenAI models by 12 November 2026, invoking a change-of-control clause after SpaceX completed its $60bn acquisition of the AI coding tool on 14 August — a concrete case study in what happens when a single vendor controls the models behind your development stack.

OpenAI has told Anysphere, the company behind Cursor, that it will end Cursor’s access to OpenAI’s models by 12 November 2026. The trigger is a change-of-control clause in their contract: SpaceX completed its $60bn all-stock acquisition of Anysphere on 14 August, and OpenAI notified SpaceX of the wind-down two weeks later, on 28 August. OpenAI’s stated reasoning is blunt — it says it can’t be confident SpaceX will use its technology within OpenAI’s terms of service, pointing to prior contract violations tied to Musk-controlled companies (Twitter/X, xAI). Anthropic has already stepped in to backfill compute for Cursor, and the practical disruption looks contained: OpenAI’s models reportedly serve only around 5% of Cursor’s user traffic today.

Why the size of the impact isn’t the point

A 5% traffic share sounds like a footnote, but the mechanism behind it is what matters. Cursor didn’t do anything to trigger this — its own parent company changed hands, and a completely separate vendor pulled its models as a consequence. That’s the risk every team takes on when a development workflow depends on a specific AI coding tool’s access to a specific model: the terms can change for reasons that have nothing to do with your product, your usage, or your contract with the tool itself. It’s the same lesson the SpaceX-Cursor deal itself first raised back in July, now playing out as an actual cutoff with a real date attached.

So what

If your team — or an agency building for you — has quietly standardised on one AI coding tool tied to one model vendor, this is worth a five-minute gut check: what breaks if that pairing changes, and how much of your delivery timeline depends on it not changing? Model-agnostic tooling and a documented fallback plan aren’t paranoia, they’re basic vendor risk management for anything built with AI assistance in 2026. It’s part of what we weigh in on for clients through our AI-assisted development work — if you want your build’s AI tooling choices stress-tested before they become a dependency, get in touch.

← All research

More research.

GitHub Copilot SDK is becoming the Microsoft Copilot SDK: what builders of AI products should know

On 28 October 2026 GitHub said its Copilot SDK is being renamed Microsoft Copilot SDK, the programmable layer for the shared Microsoft and GitHub agent harness. No immediate action is needed.

Read ›

GitHub Agent Merge: Copilot now watches your pull requests and fixes what blocks the merge

On 28 October 2026 GitHub added Agent Merge to pull requests: a 'Watch and fix' option where Copilot repairs failing Actions workflows and merge conflicts in the cloud, optionally with auto-merge.

Read ›

Claude Code 2.1.314 adds a setting that blocks AI file writes outside the project folder

Claude Code 2.1.314 (30 October 2026) adds permissions.blockWritesOutsideWorkingDirectories, so Claude's file-editing tools refuse any path outside the project in every permission mode.

Read ›

GitHub Enterprise now includes Copilot: seats are bundled, AI usage moves to your budget

From 28 October 2026 account-team customers can get Copilot included with every GitHub Enterprise licence, with AI usage metered against an enterprise budget from the first request. Standalone Copilot is $10 per user per month.

Read ›

GitHub Copilot Fusion goes GA: one pick, many models, and a 30% launch discount

On 28 October 2026 GitHub made Copilot Fusion generally available: instead of choosing a model, developers pick an effort level and Copilot routes each task across models. Paid plans get 30% off model costs for a limited time.

Read ›

GitHub Agentic Workflows is generally available: automations written in plain Markdown

On 28 October 2026 GitHub made Agentic Workflows generally available: AI agents that triage issues, analyse CI failures and update docs, defined in Markdown and run inside GitHub Actions with read-only defaults.

Read ›

Start a project

Building with AI? Let's talk.

Tell us what you are building. We'll give you an honest view of the right approach.

Start a projectSee our work