The most symbolically timed launch in developer tools this year happened by accident. On August 17, Cursor opened Origin — its own code hosting and collaboration platform — to paying users. Hours later, GitHub began its worst outage in recent memory: seven and a half hours of degraded service, with error rates around 20% on the web and API and roughly 50% on archive downloads. The internet promptly declared "Cursor killed GitHub."
Neither event is the real story. The real signal: code hosting is becoming the infrastructure layer of AI-agent-driven development, and the competitive frontier of AI coding has moved from "who writes better code" to "who owns the entire workflow."
What Origin actually is
Origin is Cursor's own repository hosting and collaboration platform. Developers can create repositories, push local projects, and use Pull Requests, code browsing, diff, comments, code review, and merge — a complete collaboration flow that previously lived on GitHub.
But Origin is not a GitHub clone. Its defining move: code, Pull Requests, and Cursor's Agent now share one environment. As Cursor's changelog puts it, "Your code, your pull requests, and your agent now live in one place." Developers can ask the AI questions about the file on screen, have the agent modify code, create or update PRs, and push commits. The human's role shifts toward specifying requirements, reviewing results, and making final calls.
Origin also plugs into the surrounding pipeline — Vercel, Buildkite, Depot — so work flows from writing to review to testing to deployment inside one workflow.
The wedge strategy: GitHub sync
Origin's cleverest feature is GitHub sync. It mirrors GitHub repositories into Origin in real time while keeping GitHub as the authoritative source for existing projects. Icons mark which repositories are Cursor-hosted and which still come from GitHub.
This is a textbook wedge strategy, as VentureBeat noted. A full source-control migration is one of the riskiest projects an engineering organization can undertake — CI pipelines, compliance records, audit trails, branch protection, third-party integrations, and the habit change of every engineer. No CTO approves that for a beta product. A read-only mirror costs almost nothing to try and nothing to abandon. It quietly shifts the surface where developers do their daily work. If Origin's review experience is genuinely better — and Cursor is spending heavily to make sure it is — the source-of-truth status eventually follows developer attention.
A perfectly timed collision
The outage began at 13:40 UTC on August 17 and was declared resolved at 21:15 UTC. Pull Requests, Issues, Actions, API, Webhooks, Pages, and Git operations were affected, and Copilot took hits too; enterprise features such as SAML, OIDC, SCIM, and Team Sync also degraded.
The timing produced a day of jokes. Vercel CEO Guillermo Rauch quipped on X that unlike GitHub, Origin "still works." Cursor employee Matt Palmer wrote the line of the day: "We planned to launch this earlier — but GitHub went down."
The collision is symbolic, not causal. One outage will not unseat GitHub, whose ecosystem and enterprise base dwarf a beta platform. But it did two things: it reminded everyone how concentrated the world's code infrastructure is, and it handed the challenger a global spotlight on day one. The same logic — the next layer of value is the layer that coordinates work — applies to AI organizations as a whole: Collective AGI: why AI's next layer is organization.
The competition just moved up the stack
For years, AI coding tools competed on a single question: who generates better code? Origin's launch signals that the contest has moved up the stack. The questions now: who runs the agents, who reviews their work, who hosts the repositories, and who ultimately controls the development process.
GitHub is not idle — features like Stacked PRs show it is adapting to agent-heavy, complex work. But Origin's developer Tomas Reimers (a Graphite co-founder) told Hacker News that the coming weeks will focus on deeper agent integration: understanding agent-written code without requiring humans to read every line, and automatically advancing PRs to a mergeable state.
The frame shift echoes the moment GitHub displaced SVN-era hosting. The winner was not the best repository, but the platform that became the default operating system for how code gets made. Origin's bet: in the agent era, that operating system includes the agents themselves.
What to watch next
- Review experience. The wedge only works if the mirrored workflow becomes the primary one. Watch whether Origin's AI-assisted review genuinely beats GitHub's.
- The agent-to-PR loop. If agents can advance PRs to a mergeable state with humans as veto — not author — review tooling becomes the moat.
- GitHub's answer. Expect agent-first features to accelerate. Stacked PRs was a hint, not the end.
- For teams. Do not migrate yet. Run a sync mirror on a side project and measure whether in-repo agents actually save review time. Origin is designed to destroy switching costs; the only way to evaluate it is to make switching nearly free.
