Cursor Origin: Default Settings and Data Terms
Cursor Origin is turned on by default for paid users, but its data terms remain unpublished.
Launch and GitHub Outage
On Monday morning, Cursor began rolling out its own code hosting platform, Origin. Approximately three and a half hours later, GitHub experienced a significant outage that lasted for six hours and forty-two minutes, resolving at 20:22 UTC.
The Coincidence
The timing of the launch and GitHub’s downtime led to an ironic twist. While Cursor intended to ship earlier, the coincidence worked in their favor as most of the internet reversed the order.
"It is a joke, and a good one," Matt Palmer, a Cursor employee, quipped on Twitter, referencing his company’s launch tweet.
What Went Wrong with GitHub?
GitHub’s degradation impacted various services:
- Error rates: Approximately 20% for pull requests, issues, and the API; around 50% for archive and raw file downloads.
- Enterprise features: SAML, OIDC, SCIM provisioning, and Team Sync all failed.
- Copilot: GitHub’s AI-powered coding assistant also encountered issues.
This outage was the seventh incident on GitHub’s status page in just fifteen days.
Cursor Origin’s Design
Cursor Origin offers repositories, pull requests, code browsing, and search. However, it does not require users to switch from GitHub entirely. Instead, it provides a mirror of GitHub repositories within its platform:
- Permissions: Mirrors GitHub’s existing read and write settings, ensuring familiarity for developers.
- Pushes and Change Source: Pushes still go to GitHub, and the changelog emphasizes that GitHub remains the source of truth for changes initiated there. Pull request comments, however, sync bidirectionally within seconds.
- Integration: Existing GitHub Actions workflows run unchanged on Depot and Buildkite, while Vercel handles preview deployments.
The Strategy Behind Compatibility
Cursor’s strategy revolves around compatibility with GitHub, making it a low-risk option for early beta testing. By keeping the source control system in place, Cursor addresses the risk associated with migrating to a new platform.
Agentic Era and AI Adoption
In June, Cursor announced Origin as a git forge for the agentic era, demonstrating remarkable agent performance during a demo. The actual numbers are even more impressive:
- Pull Request Automation: Agents running autonomously in cloud machines now open 35% of the pull requests merged within Cursor.
- Data Trends: Google’s 2025 DORA report and Stack Overflow’s developer survey highlight the growing strain of AI adoption on delivery throughput and stability, emphasizing the need for human oversight in code review processes as AI accuracy becomes more questionable.
GitHub’s Opening
An analysis by LeadDev reveals a concerning trend: 48 major GitHub incidents between May 2025 and April 2026, indicating the platform’s vulnerability to disruptions.