Back to Insights
Software AI

Cursor Launched a GitHub Rival on the Day GitHub Fell Over

Cursor's Origin puts repos, PRs and CI inside the editor, three days after SpaceX closed its $60B deal and on the day GitHub degraded for 7.5 hours.

S5 Labs Team August 17, 2026

Cursor opened the early beta of Origin to every paid plan on Monday, August 17: hosted Git repositories, pull requests, code review, merges and CI hooks, all inside the editor, with two-way sync to GitHub for teams not ready to move. The same morning, GitHub’s status page opened an incident at 6:40am Pacific that was not resolved until 2:15pm, roughly seven and a half hours later, with error rates GitHub itself put at about 20% for web and API traffic and about 50% for archive and raw-file downloads. Actions, Pull Requests, Issues, Webhooks, Pages, Git operations and Copilot were all listed as degraded during the window.

Nothing suggests the two events are connected; staged betas are usually scheduled weeks out, and nobody has produced evidence that Anysphere held a launch for a competitor’s bad day. What they share is a direction, and for anyone deciding where a team’s code should live, that deserves more attention than the timing.

Three days before Origin shipped, SpaceX closed its purchase of Anysphere. The deal was all stock, valued at $60 billion, and Cursor now sits inside the SpaceXAI division with access to SpaceX’s GPU fleet. The company most teams adopted in 2024 as an editor on top of GitHub and a few model APIs is now a vertically integrated stack under one owner: model, editor, agents, and as of Monday, the forge too.

What Origin is, and what it is not yet

Cursor’s docs call Origin “Cursor’s git forge for storing and sharing code.” Repositories live at cursor.com/codebase/{owner}/{repo}, are created and pushed through a CLI, and show up in a new Codebase tab in the desktop client. Pull requests carry a timeline, commits, checks and file diffs; you can review, comment and merge without leaving the editor. An “Ask Cursor” control puts the agent on the code you are browsing, and it can answer, make changes, update the PR or push a branch. Cloud agents run against Origin repos while your laptop is closed.

The GitHub sync is what makes the beta usable today. You connect a GitHub organization, pick repositories, and Origin keeps a live copy. GitHub stays the source of truth for a synced repo and keeps receiving pushes; comments left in Cursor appear on the GitHub PR within seconds, and vice versa. Nothing forces a migration.

Third-party wiring at launch is narrow. Vercel builds a preview deployment per PR and ships on merge. Depot and Buildkite run existing GitHub Actions workflow files, and Buildkite also supports its own native pipelines, so a team can move review and merge into Cursor without rewriting CI.

Origin is on Pro, Teams and Enterprise, not free plans, and it is on by default for those plans unless an enterprise admin opts out. Teams still on Cursor’s legacy privacy setting have to switch to the current Privacy Mode first, and Origin then inherits the namespace owner’s Privacy Mode; there is no separate privacy configuration for hosted code. A codebase name (the {owner} in the URL) cannot be changed once claimed. The docs cover namespaces, plan gating and Privacy Mode inheritance and stop there, with no retention terms, no data-residency statement, no SLA and no export tooling described. That is normal for an early beta, and it is also the list of things you would need answered before moving a production repository.

Three days after the deal closed

The SpaceX deal was announced June 16 as a $60 billion all-stock transaction, with DevOps.com reporting Cursor’s annualized B2B revenue at $2.6 billion at the time. It closed August 14. Yahoo Finance, citing the SEC Form 8-K, put the consideration at roughly 391 million SpaceX Class A shares, of which 389.3 million converted Cursor’s outstanding stock and the rest covered assumed RSUs and options. Cursor is a wholly owned unit of the SpaceXAI division, the rebranded xAI. Morgan Stanley, per the same coverage, thinks the acquisition could add up to $13 billion to SpaceX revenue by 2027.

Cursor’s own closing-day note says access to “the largest fleet of GPUs in the world” lets it “provide customers with more capable models at lower cost.” Grok 4.6, released jointly with SpaceXAI on August 12 and priced in Cursor at $2 per million input tokens and $6 per million output, is the first model presented as evidence. Grok Bot, the always-on agent product built with Cursor, went into beta the week before.

A model lab with its own compute now owns a $2.6 billion-a-year editor, ships agents that hold your logins, and hosts the repository those agents commit to. The pitch to a buyer becomes one vendor for the whole loop, which is what GitHub plus Copilot plus Azure was supposed to be.

What broke at GitHub, and what GitHub has said

The status page record is specific about symptoms and silent on cause. GitHub opened the incident at 13:40 UTC as “impacted performance for some GitHub services.” Within an hour it had listed Pull Requests, Issues, Actions, API requests, Webhooks, Pages, Git operations and Copilot as degraded and posted the 20% web/API and 50% download figures, along with impact to SAML and OIDC sign-in, SCIM and Team Sync. At 16:36 UTC GitHub said it had “identified the problematic component and have taken corrective actions.” Most services were marked mitigated by 16:59, but residual authentication failures, mostly Copilot, kept the incident open until 21:15 UTC.

What that component was, GitHub has not said. The closing update promises “a detailed root cause analysis” when available. Nothing GitHub posted on Monday attributes the outage to AI agents or to load at all, and this article does not either.

What GitHub had already said about capacity is another matter. In April, GitHub CTO Vladimir Fedorov published an availability update saying the company had started executing a plan in October 2025 to grow capacity 10X, and that “by February 2026, it was clear that we needed to design for a future that requires 30X today’s scale,” with agentic development workflows accelerating sharply since mid-December. In June, after Business Insider reported that GitHub was leaning on AWS for capacity, a Microsoft spokesperson said “the incredible spike in agentic development that began late last year has tested our infrastructure’s limits,” and that Microsoft was accelerating its Azure move while keeping a multi-cloud strategy. Both statements predate the outage by months, and neither is a root cause. What they establish is that GitHub’s own leadership has said its capacity plan was outrun by agent traffic, and that admission is a better argument for a forge built for agents than anything Cursor could have said itself on launch day.

Monday was the fifteenth incident of the month

The outage was not isolated. GitHub’s public status API lists 15 incidents between August 1 and August 17. Most were minor and short: a GraphQL timeout bump on the 11th traced to “resource contention” at one site, a PR and Issues error spike on the 12th from a database migration that removed indexes still referenced by application settings, three separate incidents on the 13th. Two were rated critical. On August 6, Actions was degraded from 15:05 UTC to 00:14 UTC the next day; GitHub’s own write-up says that at peak 71% of workflow runs hit infrastructure failures and 75% of the remainder were delayed by more than five minutes, after a routine deployment to an internal service. The second was Monday.

None of that makes GitHub unusable. It does mean that if your CI, review and merge queue run on GitHub, you have absorbed two multi-hour Actions interruptions in eleven days, and the platform’s own CTO has told you the scale it is planning for tripled between October and February. Cursor’s Depot and Buildkite hooks let a team move the run step off Actions without touching workflow files, and that reads as deliberate.

Where your code lives is now a vendor decision

For most of the past decade, “the repo is on GitHub” was not a decision anyone revisited. GitHub was the common ground that editors, CI vendors and agent frameworks integrated with, and Microsoft’s ownership was priced in as benign because Microsoft did not sell you the editor’s model. That neutrality is thinner now. Copilot is a first-party product with a first-party incentive, and Monday’s Copilot authentication tail shows how tightly forge and assistant are coupled on GitHub’s side too.

Origin proposes the opposite bargain openly: put the repository, the review, the merge and the CI trigger inside the editor where the diffs get written, and the loop gets shorter. An agent that opened the PR can be asked about it in the same pane, can address review comments, and can push the follow-up branch. For a small team shipping fast with Cursor’s cloud agents, that is a real gain, and while GitHub stays the source of truth the sync means you take it without giving anything up.

The cost is where the mirror stops being a mirror. Once Origin is the source of truth, your code, your review history and your CI hooks live with a company that also trains the model, runs the agents, and now answers to SpaceX. The same parent’s Grok Build was found in July to be uploading whole repositories, history and secrets included, when the agent had been told not to read them, and the lab never answered the transmission question directly. Origin’s docs today say nothing about retention, residency or how you leave. GitHub’s problems are operational and it publishes root causes, eventually; Origin’s are contractual and unwritten.

The decision in front of a team, then, is whether the productivity of a closed loop is worth being inside one vendor’s loop. Sync a repo, move review for one project, and route its CI through Depot or Buildkite if you want to see what the shorter loop is worth. Do not make Origin the source of truth for anything you would need to get back until Cursor puts retention, export and an SLA in writing. GitHub having a bad Monday is a good reason to build for a second forge, and by itself a poor reason to hand the first one to SpaceX.

Sources

Want to discuss this topic?

We'd love to hear about your specific challenges and how we might help.

Start a conversation