Summary
In mid-August 2026, Cursor launched Origin in early beta on paid plans: a Git forge that hosts repositories, pull requests, code browsing, and a public REST API, and can sync existing GitHub repos two-way while GitHub stays the source of truth. Origin makes coding agents first-class in the PR lifecycle and ships day-one CI integrations, with stacked pull requests and automated merge-conflict resolution carried over from Cursor's Graphite acquisition.
What changed
Cursor released Origin, its own code-hosting platform, in early beta for Pro, Teams, and Enterprise plans: native repos, pull requests, branch protections, a public REST API, and two-way GitHub sync. Agents operate in the same surface as code and PRs (answering questions, revising from review comments, pushing branches). It carries over stacked PRs and automated merge-conflict resolution from the Graphite acquisition, cites roughly 296,000 clones per hour and 22 commits per second per repository, and launches with Vercel preview deployments, Depot, and Buildkite integrations.
Why it matters
Cursor moving from AI editor into code hosting turns it into a fuller platform for agent-driven development, and its debut during a GitHub outage underscored demand for hosting alternatives built for agent scale. GitHub-sync-first onboarding lets teams trial hosting without migrating, lowering switching cost while Cursor captures more of the PR and review workflow.
Evidence excerpt
Connected GitHub repositories remain on GitHub as the source of truth, permissions mirror GitHub access settings, and pull request conversations sync both ways within seconds. Origin claims roughly 296,000 clones per hour and 22 commits per second per repository, with stacked pull requests and automated merge-conflict resolution from Cursor's Graphite acquisition; Vercel, Depot, and Buildkite integrations are live on day one.