Cursor Origin started rolling out on Monday morning as a code hosting platform with repositories, pull requests, code browsing and search. About three and a half hours later, GitHub began a degradation that lasted more than six and a half hours. The order matters, because much of the internet reversed it: many assumed Origin had caused or exploited the outage. In fact, Origin had already shipped. A Cursor employee later joked that the company had wanted to launch earlier, but GitHub was down. The joke traveled further than the product itself.
Key facts at a glance
- Cursor Origin launched on Monday morning; GitHub suffered a major outage hours later.
- GitHub's incident lasted 6 hours 42 minutes, with 20% error rates on pull requests, issues, and API calls.
- Origin uses GitHub as the source of truth and syncs pull request comments both ways.
- Autonomous agents now open 35% of pull requests merged inside Cursor.
- Origin is enabled by default for paid users, with no published data retention or residency terms.
- SpaceX closed its Cursor acquisition on 14 August, three days before Origin shipped.
What actually broke on GitHub
GitHub's incident ran for six hours and forty-two minutes, ending at 20:22 UTC. During that window, error rates hit roughly 20 percent on pull requests, issues and the API. Archive and raw file downloads were worse, with error rates around 50 percent. Enterprise single sign-on was affected too, taking down SAML, OIDC, SCIM provisioning and Team Sync. Copilot also failed. The status page later listed it as the seventh incident in fifteen days.
The wedge is the design
Cursor Origin is not trying to force anyone off GitHub. That is its most interesting decision. After connecting an organization, users can choose repositories and see them alongside Origin-native ones. Permissions mirror the read and write settings already configured in GitHub. Push operations continue to go to GitHub, and the changelog says GitHub remains the source of truth for anything started there. Pull request comments sync back and forth within seconds.
Compatibility extends to the surrounding toolchain. Depot and Buildkite can run existing GitHub Actions workflows unchanged. Vercel handles preview deployments. The message is clear: keep GitHub if you want, but do your daily work inside Cursor.
That approach is the entire strategy. Replacing source control is one of the riskiest projects an engineering organization can attempt, and few chief technology officers would approve it for an early beta. A read-mostly mirror, on the other hand, approves itself. It costs nothing to try, leaves the source of truth untouched, and quietly moves developers into a new environment where Cursor controls more of the workflow.
The agent argument is real
Cursor first announced Origin in June at its developer conference, pitching it as a git forge for the agentic era. The launch demo showed agents running at 22.6 commits per second against a single repository. That was an impressive number, but a supporting statistic matters more: agents running autonomously in cloud machines now open 35 percent of the pull requests merged inside Cursor, according to industry reporting.
That changes what a pull request means. A forge designed for humans assumes a pull request carries human intent. Reviewers can ask the author what they meant. When a third of merged changes come from software, the review queue stops being a conversation and becomes a scheduling problem. The queue has to route work, verify behavior, and decide whether an automated change is safe without a human author in the loop.
Independent research supports the strain. The 2025 DORA report found that AI adoption correlates positively with delivery throughput but negatively with delivery stability. Stack Overflow's survey of 49,009 developers found trust in AI accuracy fell to 33 percent from 43 percent. Those numbers explain why Cursor built Origin rather than simply adding more agent features to an editor. It wants to control the entire loop where agents write, review, and merge code.
GitHub earned the opening
GitHub's outage was not an isolated event. One industry analysis counted 257 GitHub incidents between May 2025 and April 2026, 48 of them major. That is roughly one significant disruption per week. GitHub Actions alone accounted for 57 outages in twelve months.
GitHub has acknowledged the problem. Its chief technology officer, Vlad Fedorov, said the platform never anticipated its current scale. An engineering post in April conceded that GitHub had failed to meet its own reliability standards. Users have already moved. The Zig project went to Codeberg in November, and Mitchell Hashimoto announced in April that Ghostty would follow. OpenAI has reportedly begun building its own alternative partly because outages left engineers unable to commit.
GitHub has also lacked a chief executive for about a year, after Thomas Dohmke resigned. Microsoft folded the unit into its CoreAI organization. The result is a popular platform with growing reliability concerns and unclear leadership, exactly the environment Cursor Origin needs.
The question Cursor has not answered
Here is the part that deserves a security review rather than a news cycle. Cursor Origin reaches all paid plan users from Monday, except enterprise organizations whose administrators opt out. That is opt-out, not opt-in. Plenty of companies have never decided whether proprietary code may sit on a new host. Cursor has now decided for them.
Cursor has published nothing about data retention, residency, training use, subprocessors, or migration tooling. The documentation covers namespaces, plan gating, and privacy mode inheritance, then stops. Enterprises need to know where repositories are stored, who has access, and whether code samples are used to train models. Without those terms, adopting Origin means accepting unknown data handling.
The ownership context makes the silence more significant. SpaceX closed the Cursor deal on 14 August, three days before Origin shipped. Cursor now sits in a division called SpaceXAI. SpaceX made the takeover official in June at $60 billion, and regulators had already asked gun-jumping questions about the two companies working together early. Critics have noted that xAI's models and its approach to guardrails differ from what Cursor has historically stood for. One company would then control the editor where agents write code, the host where that code lives, and the model those agents run on.
One more thing on the record
Researchers at Mindgard disclosed in July that Cursor would execute a malicious git.exe placed in a Windows project root the moment a user opened the project, with no prompt. They first reported it in December. Cursor declined to patch, calling the issue out of scope under a shared responsibility model, and conceded it had not closed the loop with the researcher promptly. No CVE exists.
The same flaw class appeared in GitHub Copilot CLI, Gemini CLI, and OpenAI Codex. It is not a Cursor problem alone, but it is an awkward footnote for a product asking to hold repositories.
What would settle it
Three things would settle the debate, and none of them is the outage. First, organizations should confirm their own posture this week, because the default is on. Second, they should read the data terms when they exist and treat Origin as a convenience layer over GitHub until they do. That is already what the architecture makes it, with GitHub as the source of truth and comments syncing both ways. Third, they should ask about egress now, while the mirror is still a mirror. Cursor raised prices last month, and the properties that make Origin safe to adopt are the ones most likely to erode as Cursor's incentives shift toward owning the substrate rather than borrowing it.