Cursor Origin is a new Git forge built into Cursor, launched in early beta on August 17, 2026, available on Pro, Teams, and Enterprise plans. It hosts Git repositories, browser-based code browsing, pull requests, branch protections, a CLI, and a REST API, and lets Cursor's cloud agents work directly against repositories. Teams can either host repositories natively on Origin or mirror an existing GitHub repository, with GitHub remaining the source of truth and bidirectional pull-request sync between the two. Native Origin repos support only Internal and Private visibility (no public repos yet), and CI/deployment integrations are limited to Vercel, Depot, and Buildkite, with mirrored repos keeping GitHub Actions, secrets, and Issues on GitHub. The recommended approach is to mirror an existing repo first and test the full agent-to-pull-request workflow before considering a full migration.
Table of contents
What is Cursor Origin?Origin does not replace GitThere are 2 ways to use OriginThe Codebase is the home for your repositoriesCreating an Origin repositoryInstalling the Origin CLICreating and cloning repositories from the terminalBrowsing and searching codePull requests in OriginHow GitHub mirroring worksMirrored pull requests sync both waysGitHub remains the source of truthAgents are part of the repository workflowAutomations can react to repository eventsDeployments and CIRepository permissions and protectionsOrigin also has a public APIIs Origin a GitHub replacement?How I would use Cursor OriginWhen Origin is a good fitWhen I would waitThe interesting part of OriginQuestions this post answers
What is Cursor Origin and how is it different from using Cursor with GitHub?
Cursor Origin is a Git forge built directly into Cursor that can host repositories, pull requests, and coding agents in one system, rather than Cursor connecting to code hosted externally on GitHub, GitLab, or Bitbucket. It launched in early beta on August 17, 2026, on Pro, Teams, and Enterprise plans, and includes code browsing, branch protections, a CLI, and a REST API. daily.dev surfaces coverage like this for developers deciding whether to adopt new AI-native git hosting workflows.
Can I mirror an existing GitHub repository into Cursor Origin without moving it off GitHub?
Yes, GitHub mirroring copies Git history, branches, tags, code, and pull requests into Origin while GitHub stays the source of truth, so pushes made through the Origin remote still go to GitHub. Issues, Actions workflows, and Actions secrets remain on GitHub only. Pull request comments and reviews sync bidirectionally between Origin and GitHub within seconds. teams weighing a gradual migration off GitHub can track these hosting changes on daily.dev.
Does Cursor Origin support public open source repositories?
Not yet during early beta; the documented repository creation flow only offers Internal and Private visibility levels, with no public option. Internal makes a repo visible to anyone with codebase access, while Private restricts it to specifically granted people, making Origin currently suited for private team work rather than public open source projects. open source maintainers evaluating new git forges can follow feature rollouts like this via daily.dev.