OpenAI is cutting off Cursor. A tool you rent can be switched off.

On August 29, 2026, OpenAI published a decision about Cursor, the popular AI code editor. The short version: OpenAI plans to stop supplying its models to Cursor. This lands about two weeks after SpaceX closed its reported $60 billion acquisition of Anysphere, Cursor's legal parent, a deal that closed around August 14, 2026.

We are going to do two things here. First, give you the verified facts, with dates and the exact language OpenAI used, and nothing invented. Second, give you an honest read on what it means for anyone who codes with an AI tool they do not control. We sell a competing tool, so weigh our take accordingly. The facts stand on their own, and we link every source at the bottom.

What actually happened

Here is the timeline, stripped to the load-bearing facts.

• SpaceX bought Cursor's parent. SpaceX closed its reported $60 billion acquisition of Anysphere, the company behind Cursor, around August 14, 2026.
• OpenAI invoked a change-of-control clause. About two weeks later, OpenAI pointed to a change-of-control clause in its terms. That kind of clause lets a vendor reconsider a contract when the other side changes owners.
• OpenAI's stated reason. In its own words, OpenAI said it “cannot be confident” that the new owner will use its technology within OpenAI's terms of service.
• The cutoff date. OpenAI proposed cutting off model supply to Cursor on November 12, 2026. It also said it will withhold its future models from Cursor.
• Corroboration. CNBC reported the decision on August 29, 2026, alongside OpenAI's own published statement.

Read that reason again, because it is the tell. Nothing OpenAI said is about Cursor's product, Cursor's users, or the quality of Cursor's editor. It is about who signs the checks now. The SpaceX Cursor acquisition changed the owner, and the owner change was enough.

A tool you rent can be switched off by strangers

Here is what should bother you, whichever editor you use. No Cursor user was part of this decision. You did not sign a contract with OpenAI. You did not vote on the SpaceX acquisition. But the outcome of a dispute between OpenAI and SpaceX can degrade the tool you open every morning.

That is what renting means. When your coding tool is a thin client over someone else's models, your workflow depends on a supply chain of business relationships you cannot see and cannot control. A pricing change, an acquisition, a change-of-control clause, a strategy meeting in a building you will never enter: any of these can reach into your editor and change how it works, or whether it works at all.

Cursor is a good product with a real team. This is not a knock on their engineering. It is a structural problem. If the model lives on someone else's servers and the contract lives between two other companies, you are a passenger. AI coding tool vendor lock-in is not a bug you can file. It is the shape of the arrangement. The only real defense is an AI coding assistant that cannot be shut off by someone else, because you own the parts that matter.

This is the pattern, not a one-off

If this were the only time a coding tool got yanked around by forces outside a developer's control, you could call it bad luck. It is not the only time. It is the third or fourth this year.

• Continue.dev. Cursor itself acqui-hired Continue.dev in mid-2026 and wound the standalone product down. Users got an export deadline, then it was gone. We wrote that one up in Cursor acquiring Continue.dev.
• Gemini CLI. Google retired the standalone Gemini CLI and folded it into the cloud-gated Antigravity CLI. You could own your terminal, or you could rent it. We covered it in the Gemini CLI shutdown.
• Roo Code and Augment. Roo Code was sunset. Augment's completions product was sunset. Tools people had built habits around, switched off.
• The bigger squeeze. The same month OpenAI moved on Cursor, NVIDIA reportedly agreed to acquire Hugging Face, the main hub for open models, for around $13 billion. That deal is reported, not yet closed, so treat it as a signal rather than a settled fact. But the direction is clear: the layer you depend on keeps getting bought.

Put the dots together. Models, editors, terminals, and the open-model hub are all consolidating into a handful of owners. Every acquisition is a fresh change-of-control clause waiting to be invoked. If your tools sit on top of that layer, your tools inherit that risk, and you find out about it after the fact.

Rented cloud tool vs. local-first, BYOLLM

Same coding work, two very different foundations. The columns below are not about features. They are about who can turn your tool off.

The right column is not magic. It is just a different arrangement. When you bring your own LLM and run the tool on your own machine, an argument between OpenAI and SpaceX is not your problem. If one provider gets cut off or doubles its price, you switch a preset and keep coding.

What owning your AI coding stack looks like

This is the part where we are selling something, so read it with that in mind.

Bodega One Code is a local-first AI coding assistant that runs on your machine. It is a desktop IDE with a Monaco editor, an AI chat, and an autonomous coding agent, plus a command-line client. It is BYOLLM: 15+ provider presets covering local runtimes like Ollama and LM Studio, cloud providers like OpenAI, Anthropic, and Google, and custom endpoints for anything else. You bring your own keys. You point it at whatever model you want. If OpenAI cut off one tool tomorrow, you would switch to a different preset or a local model and keep working. See the full list on the BYOLLM page.

It runs on your machine, so your code stays on your machine. Air-gap mode blocks network egress entirely, which is about as far from a change-of-control clause as you can get. There is no subscription. Right now it is a free open beta for everyone, commercial use included. At full release, Personal stays free and a one-time Pro license (price to be announced) unlocks commercial use. Pro is not on sale today, and we are not going to quote a number we have not locked.

Now the honest caveats. It is in open beta, so expect rough edges and file bugs when you hit them. It is not open source. If open source is your hard line, and that is a reasonable line to draw, then opencode and Aider are good calls, and we will happily point you to them. We think owning your stack matters more than any single vendor, ours included. You can download Bodega One Code and try it, or compare it directly on our Cursor alternatives page.

What to do next

You do not have to switch tools today. You do have to know where you are exposed. Three steps, in order.

1. Audit your dependencies. List every AI coding tool you rely on and, for each, write down which models it uses and who owns those models. Anywhere the model and the tool are owned by different companies, you have a change-of-control clause in your future.
2. Keep your provider config and keys portable. Use your own API keys under your own accounts, not keys bundled inside a subscription you cannot export. Store your provider settings somewhere you control so you can move them to another tool in an afternoon.
3. Try a local-first or BYOLLM option. Even if you keep your current editor, get one local-first, bring-your-own-LLM setup working so you have a fallback that no third party can switch off. A local model that runs with no network is the strongest version of that fallback, and it is how you avoid AI coding tool lock-in for good.

If you want to try the CLI, the install is one line:

curl -fsSL https://github.com/BodegaoneAI/bodegaone-cli-releases/releases/latest/download/install.sh | sh

It points at your own keys and your own models from the first command. No account with us required to run it.

Sources

• OpenAI - “Our decision on Cursor following its acquisition by SpaceX”
• CNBC - OpenAI cutting Cursor's model access (August 29, 2026)
• CNBC - the reported NVIDIA and Hugging Face deal (August 27, 2026)