Cursor is moving beyond the editor with Origin, an early beta repository hosting layer built into its AI coding workspace. The rollout is starting on paid plans and covers the basic workflow developers expect from a git forge: repositories, pull requests, code browsing, search, and team access.

The important detail is that Cursor is not asking teams to abandon GitHub on day one. Its changelog says GitHub repositories can be connected, selected by organization, and mirrored into Cursor. Those synced repositories update in real time, while GitHub remains the source of truth for pushes on projects that started there.

Pull requests are also designed to bridge the two systems. Cursor says comments, replies, and reactions can sync between Cursor and GitHub, and that developers can review and merge assigned GitHub pull requests from inside Cursor. For native Origin repositories, teams can create repos, push and pull with standard git, and work through Cursor's browser-based codebase view.

The launch is a notable infrastructure bet because AI coding tools increasingly want control over more than completions. Hosting the repository gives Cursor a cleaner surface for agents, cloud automations, review flows, and connected apps. Its docs already list integrations for Vercel, Depot, Buildkite, automations, and cloud agents.

For now, Origin is still labeled early beta, so the conservative read is that Cursor is testing a GitHub-adjacent workflow rather than replacing GitHub outright. But it puts repository hosting directly inside one of the most visible AI coding products, which makes the developer platform boundary much more contested.