DK Dark Knight 2026-08-31 5 min read

The Vertical Split: OpenAI Dumps Cursor, Cursor Builds Its Own GitHub

The AI development stack just split in half.

On Friday, OpenAI announced it will cut off model access to Cursor on November 12, citing SpaceX's $60 billion acquisition and Elon Musk's history of breaking contracts. Over the weekend, Cursor responded by launching Origin—its own AI-native code hosting platform. Repos, pull requests, code browsing, GitHub sync, and agents baked into every repository.

This isn't a product update. This is a strategic realignment. The era of choosing your model, your editor, and your host independently is ending. The walls are going up.

Timeline of the split

The sequence happened fast:

timeline
    title Cursor / SpaceX / OpenAI Timeline
    mid-Aug : SpaceX closes $60B Cursor acquisition
    Aug 17 : GitHub 7h 47m outage
    Aug 17 : Origin early beta launches
    Aug 28 : OpenAI notifies wind-down, Nov 12 cutoff
    Aug 29 : CNBC / Reuters / Bloomberg report
    Aug 31 : Origin + outage narrative crystallizes

What OpenAI actually said

OpenAI's post is worth reading in full. It's measured but explicit:

"We cannot be confident that SpaceX will use our technology within our terms of service, based on our experience with Elon Musk's companies violating contracts."

They cite three specifics:

The decision uses a change-of-control clause in the Cursor contract. OpenAI says they pushed the cancellation date as late as possible and are giving the maximum notice period provided by the agreement. They claim to care about Cursor's users—but the message is clear: you can't use our models if you're owned by people who don't follow the rules.

What Origin actually does

Origin is a git hosting platform built into Cursor. Based on the changelog and third-party coverage, here's what it ships with:

The repo URL pattern puts the codebase name front and center. The GitHub sync is bidirectional and real-time. The "app ecosystem" pitch is classic platform play—get enough repos on Origin, and the integrations lock the workflow in.

Missing from the initial launch: an API, a CLI beyond basics, team management, and any mention of open-source compatibility or export/migration tools. All standard for a beta, but worth noting.

The two stacks forming

Draw the competitive map and two vertical integrations emerge:

graph LR
    subgraph "OpenAI Stack"
        OAI[OpenAI Models
GPT-5, Astra]
        GH[GitHub
(Microsoft)]
        VS[VS Code / Copilot]
        OAI --> GH
        OAI --> VS
    end

    subgraph "SpaceX / Cursor Stack"
        C[Editor]
        O[Origin
Code Hosting]
        G[Grok / Model A]
        A[Agent Layer]
        C --> O
        C --> G
        C --> A
        O --> A
    end

On one side: OpenAI models + GitHub (Microsoft) + Copilot/VS Code. On the other: Cursor editor + Origin repos + Grok + a 1.5-trillion-parameter Model A reportedly in training at SpaceX. Add Cursor's cloud agents, iOS app, and the "Automations" feature that lets agents run on schedules, and you have a full-stack platform that never leaves the Cursor perimeter.

The 5% figure from Cursor's CEO is the key number. If OpenAI accounts for only 5% of user traffic, Origin isn't replacing GitHub yet—it's replacing OpenAI's dependency. Cursor is betting that local + Grok + whatever SpaceX is training can cover the gap, and that owning the repo layer gives them leverage the editor alone never could.

The code custody question

Here's the uncomfortable question nobody in the coverage is asking directly: what happens to your code when Origin is the repo, Cursor is the editor, Grok is the model, and SpaceX owns all three?

Open-source advocates are already raising concerns about the opt-out rollout model and unclear code-custody terms. The opensourceforu piece flags "unclear code-custody terms" as a risk. When the entire pipeline—edit, model inference, code storage, agent execution—runs through a single provider, the provider sees everything. GitHub had similar concerns under Microsoft, but the AI dimension changes the equation: the agent doesn't just store your code, it reads and acts on it.

Compare with the OpenAI stack: Microsoft owns GitHub and has Copilot integration, but the model runs on Azure and the editor is a separate product. There are seams. The SpaceX/Cursor stack has no seams.

Bottom line

This week marks the first major realignment of the AI coding tool market since Copilot launched. OpenAI drew a boundary line around who can use its models. Cursor responded by building the moat it can control—the repo layer. Two vertical stacks are forming, and developers who have been enjoying "pick any model, any editor, any host" are about to discover that those choices have geopolitical and corporate strings attached.

The 5% number is Cursor's hedge. If it's real, Origin is about independence from OpenAI, not a GitHub replacement. But if Model A delivers and the agent features compound, the Origin-hosted repo becomes the center of gravity that keeps everything in the SpaceX/Cursor orbit. That's the bet.

For now: if you're a Cursor user, you have until November 12 to figure out your model strategy. And if you're putting code on Origin, read the terms carefully. The seams aren't there yet.

Related reading