Cursor Origin: The Git Forge Built for AI Agents, Explained

Cursor Origin is Cursor's own git forge — a place to host repositories, review pull requests, and browse code, with Cursor's coding agents wired in as first-class actors. It shipped in early beta on August 17, 2026, on paid plans only. This guide covers what actually launched, how the GitHub mirror works, what the agents can do, and — just as important — what's still missing. Everything here is grounded in Cursor's own documentation.

What is Cursor Origin?

Cursor describes Origin in one line: a git forge for the agentic era. In plain terms, it's a real git host — not a UI skin over GitHub. Repositories live on Cursor's own remotes, and you push and pull with standard git.

The reason a company known for an editor is suddenly hosting code: the repository is where agent work becomes real, reviewable, and mergeable. With Origin, Cursor is moving into the layer where repositories, pull requests, code browsing, and agents live together — and the bigger bet is not simply to build another GitHub, but to make the forge itself part of the agent workflow rather than an external system the editor integrates with.

Origin was built by the team behind Graphite, the stacked-diff code-review company Cursor acquired, and it landed the same week as a major GitHub outage — which amplified the launch but wasn't the point of it.

What shipped in the early beta

The beta is deliberately modest. Here's what's in — and what's out.

In the beta:

• Repository hosting over standard git (HTTPS), with Internal and Private visibility
• Pull requests with inline review, checks, and merge protections
• Code browsing, search, and commit history at cursor.com/codebase
• GitHub mirroring with two-way PR sync
• An Origin CLI, API, and webhooks
• Three integrations: Vercel (preview deploys), Depot, and Buildkite (CI)

Not in the beta:

• GitHub Issues, projects, discussions, or a wiki
• Public repositories (no open-source home yet)
• A native CI runner, package registry, or releases
• Security scanning or dependency-alert equivalents
• Published storage limits, SLA, or post-beta pricing

Three integrations shipped on day one: Vercel spins up a preview deployment for every pull request and ships to production on merge, while Depot and Buildkite run continuous integration — and critically, both execute existing GitHub Actions workflows unchanged. That compatibility layer is the strategy in miniature: try Origin without rewriting your build system.

Who can use it

Origin code storage is available on Pro, Teams, and Enterprise plans — not on free plans. Access rolls out in stages, so paid subscribers may not see it immediately. Enable it by claiming a codebase name, the namespace all your repos live under. Choose it carefully: during the beta, it can't be renamed, and it appears in every repository URL.

Does Origin replace GitHub? How the mirror works

Not yet — and Cursor doesn't ask you to. The designed path is mirroring, and it's conservative in a good way. Cursor does not ask you to leave GitHub: connect a GitHub organization, pick repositories, and they appear alongside Origin-native ones.

Mirroring copies full history, branches, and tags into Origin and keeps them synced, with pull request comments and reviews flowing both directions. The crucial detail: a developer can clone from Origin and push to the Origin remote, but those pushes pass through to GitHub — and Cursor states explicitly that GitHub remains the source of truth for repositories that began there.

The bridge has boundaries. GitHub Issues are not migrated. Neither are Actions secrets or runtime config — mirrored repos keep their CI on GitHub. When a team decides Origin should be authoritative, it detaches the mirror: sync stops, the Origin copy becomes independent, and the original GitHub repo is left untouched. That detach is the real migration moment; everything before it is a free trial of the workflow.

Agents as first-class actors

The feature list above could describe any young forge. The strategy shows in the agent wiring. Cursor's cloud agents can create an Origin repository end to end, then clone, branch, commit, push, and open pull requests against it.

Automations attach agents to repository events — a push to main, a PR opened or updated, or a schedule. And since the August 19, 2026 changelog, cloud agents automatically subscribe to the PRs they create: a subscribed agent monitors CI, fixes failed checks, responds to review feedback, and wakes when the PR changes, pursuing the goal until the work is actually done.

That closes a loop no third-party forge can offer Cursor: repository event → agent runs in an isolated VM → code change → PR update → CI result → agent wakes again. Owning the forge means owning every hop. It's worth being precise, though: the PR review model itself is still conventional human review. The bet is on where the loop tightens from here.

The honest limitations

Cursor's own docs are candid, and the gaps matter if you're evaluating a move:

• No Issues or work tracking. They don't even mirror — your tracker stays where it is.
• No public repositories. Open-source projects have nowhere to land yet.
• No native CI, packages, or security tooling. CI comes from partners; there's no documented equivalent of secret scanning or dependency alerts.
• No published limits, SLA, or post-beta price. Storage, bandwidth, and uptime commitments are unwritten as of the beta.
• Rollout is staged and admin-gated. Legacy privacy mode blocks it entirely, and team admins can disable it.

None of this is a knock on a days-old beta — it's just the honest map of where the edges are. For a fuller picture of enterprise concerns, VentureBeat's launch analysis walks through the security-review questions a platform team should ask.

Should you move your repos now?

The low-risk path is the designed one: mirror a few repositories while GitHub stays authoritative, use Origin for browsing, review, and agent workflows, and only consider detaching after you've validated CI, access controls, and the collaboration features you'd lose. The beta costs nothing beyond your existing Cursor plan, so it's a cheap preview of how agent-era infrastructure feels.

If you're curious how Cursor got here, our Cursor origin story traces the company from a CAD idea to one of the most-used AI coding tools — useful context for why it's now building its own forge.

Build your own agent workflow — on your terms

Origin's real thesis is that the interesting unit of work is a standing agent that owns a task from event to merged PR, not a chat window. That's the same bet Eigent makes — except Eigent runs a whole multi-agent workforce locally, on code and workflows you control, with no vendor lock-in. If reviewing agent-authored pull requests is your bottleneck, our review GitHub PRs workflow puts an agent on that job directly. Download Eigent and hand a real multi-step task to your own AI workforce.