Cursor Origin launches as GitHub logs its 7th incident in 15 days
Cursor rolled out Origin, its new code hosting platform, to paid users on a Monday morning. About three and a half hours later, GitHub’s status page recorded what became a six-hour-forty-two-minute global degradation: error rates near 20% across pull requests, issues, and the API, and near 50% on archive and raw file downloads. Enterprise SSO (SAML, OIDC, SCIM, Team Sync) went down with it. So did Copilot. It was GitHub’s seventh incident in fifteen days.
Matt Palmer, who works at Cursor, quote-tweeted his own company’s launch with the line: “We were going to ship this earlier, but GitHub was down.” A GitHub outage, in other words, delayed the launch of a GitHub competitor. The timing was coincidental. The argument it made was not.
️ What Origin actually is
Origin lives inside a new Codebase tab in Cursor. Teams push repositories over the command line, get the standard forge machinery (pull requests, timelines, diffs, checks, merges), and then get the part that makes it different: agents operate in the same surface as the code and PRs they are modifying. A developer can hand a review comment to an agent and have it revise the pull request in place, without leaving the editor.
Three integrations shipped on day one. Vercel spins up preview deployments per pull request and ships to production on merge, available in public beta for Pro and Enterprise customers. Depot and Buildkite handle CI, and both run existing GitHub Actions workflows unchanged. Buildkite adds native pipelines on top. The compatibility layer is intentional: Cursor is not asking teams to rewrite their build system, just to try a second window onto code they already have.
The numbers driving the product
The internal stat that best explains why Origin exists: 35% of pull requests merged inside Cursor were opened by agents running autonomously in cloud virtual machines, according to RuntimeWire. When a third of merged changes come from software rather than people, the review queue stops being a conversation and becomes a scheduling problem. That is the architectural argument Cursor is making.
The broader data backs the tension up. Google’s 2025 DORA report, drawn from nearly 5,000 technology professionals, found that AI adoption showed a positive relationship with delivery throughput and a negative one with delivery stability. More output, more breakage. Stack Overflow’s 2025 developer survey of 49,009 respondents found trust in AI accuracy had fallen to 33% from 43% year over year, while distrust climbed to 46% from 31%. GitLab’s ninth annual DevSecOps survey found 73% had hit problems with vibe-coded output and only 37% would let AI handle daily tasks without human review.
GitHub’s own Octoverse 2025 counted 43.2 million pull requests merged per month, up 23% year over year. A platform built for that volume while simultaneously struggling with reliability is a real opening. A LeadDev analysis counted 257 GitHub incidents between May 2025 and April 2026, 48 of them major. GitHub CTO Vlad Fedorov has said the platform “wasn’t built for the scale it’s now being asked to handle” and must design for 30 times today’s load.
The ownership question engineering leaders should not skip
Three days before Origin shipped, Bloomberg reported that SpaceX completed its $60 billion all-stock acquisition of Cursor. Cursor now operates inside a division called SpaceXAI, which also absorbed xAI six months earlier. The vendor asking to hold proprietary source code is now a unit of a rocket company with its own frontier-model division.
Moor Insights & Strategy analyst Jason Andersen raised the model-routing question before the deal closed: “xAI’s models and treatment of guardrails are very different than what Cursor has stood for.” As of launch, Origin’s pricing, security architecture, data-handling terms, and migration tooling were all unpublished. The changelog says only that Origin is live for “all paid plan users starting today, except enterprise orgs whose admins opt out.” Opt-out, not opt-in.
Three things to settle before Origin touches anything real
- Check your default posture now. Origin switched on for all paid users unless an enterprise admin opted out. If your org has not made an affirmative decision about mirroring proprietary code to a new host, that decision was made for you.
- Do not treat a product page as a contract. Retention, residency, training use, subprocessors, and what changes under SpaceX ownership are all unpublished. Until those terms exist in writing, treat Origin as a convenience layer over GitHub rather than a system of record.
- Ask about egress while the mirror is still a mirror. Origin’s GitHub-as-source-of-truth design is the property that makes it safe to evaluate. Ask what exit looks like now, before Cursor’s incentives shift toward owning the substrate rather than borrowing it.
There is also a disclosed vulnerability worth noting. In July, researchers at Mindgard reported that Cursor would execute a malicious git.exe planted in a Windows project’s root the moment a user opened it, with no prompt. The flaw was first reported to Cursor in December 2025. Cursor declined to patch it, calling the issue out of scope under a shared-responsibility model. No CVE was issued.
The context behind the competitor
Defections from GitHub started before Origin existed. The Zig programming language moved to Codeberg in November 2025, citing Actions failures. In April, Mitchell Hashimoto announced that Ghostty, a terminal emulator with more than 52,000 stars, would leave too, pointing to near-daily outages blocking reviews and CI. The Information reported in March that OpenAI began building its own GitHub alternative partly because outages left engineers unable to commit for hours at a time.
Cursor bought code review startup Graphite in December 2025 for what Axios reported was well above its $290 million Series B valuation. Graphite co-founder Tomas Reimers unveiled Origin at Cursor’s inaugural Compile conference in June and leads its development. The product is a beta. GitHub’s outage resolved at 20:22 UTC. Availability is an engineering problem. Who holds your source code and what they may do with it carries no such timestamp.
I’m founder of BizStack at Cagri Sarigoz LLC and a passionate advocate for entrepreneurs.
With over 14 years in tech, marketing, and AI, including my role as Head of SEO at CitizenShipper and co-founder of TaleBot at Intale AI, I’m dedicated to sharing genuine, useful product insights and tips.
At BizStack, I aim to cut through the digital noise to provide clear, actionable advice.
And more than all else, I’m a father to a (always) little girl and a husband.
Contact me at [email protected] for assistance.
