Cursor is now hosting code itself: Origin, an early beta service that syncs two way with GitHub, with launch partners including Vercel (preview deploys), Depot (builds), and Buildkite (CI).
Cursor, the AI coding editor, has a new code-hosting service called Origin — and it syncs two-way with GitHub. Origin is rolling out in early beta to all paid plans, letting teams that already use GitHub keep their repos and history there while working from Cursor's surface.
Cursor, the AI coding editor, is now hosting code itself. Origin, a new code-hosting service, is rolling out in early beta to all paid plans, with two-way sync to GitHub for any repos that started there. Cursor's stated rationale is that an AI coding agent works best when the editor, the repo, and the pull request share one surface.
The first version covers the basics: repos, pull requests, code browsing, and GitHub sync. Origin-hosted repos live under a new Codebase tab, with URLs in the pattern cursor.com/codebase/<name>. Comments on a pull request in Cursor post to GitHub; reactions and replies on GitHub surface inside Cursor within seconds. Launch partners include Vercel for preview deployments per pull request, plus Depot and Buildkite, with more integrations promised. "Agent-native" features are the part that justifies the platform move. The changelog describes them as "shipping soon."
The tradeoff is legible. Repos that start in Origin live on a young host, and users are betting that Cursor, not GitHub, will own the source of truth for the projects they spin up there. For projects that already exist on GitHub, two-way sync means teams can keep their history, reviews, and audit trail where they are, and let Cursor's agent work in a parallel surface that talks back to it.