Cursor Unveils Origin Development Platform

Cursor has launched Origin, a git-based code hosting platform embedded inside its AI-powered editor, positioning it as an alternative to GitHub for teams that already work in Cursor. The platform is rolling out in early beta on Pro, Teams, and Enterprise plans, and lives inside a new Codebase tab within the Cursor application.

The official Origin documentation describes capabilities for storing and sharing code, supporting repository creation, pull requests, and browser-based code navigation. They emphasize a narrow feature set rather than a full forge.

Developers can use the Origin git guide to clone, push, and pull repositories over HTTPS or with the Origin CLI. Mirrored repositories are pulled from GitHub and kept in sync.

Cursor is pitching Origin as “agent-native infrastructure” rather than a conventional software forge. The landing page describes it as a “git forge for the agentic era,” with messaging that code is moving faster than existing infrastructure can handle.

A report stresses features such as stacked pull requests and agent-aware merge queues, helped by Cursor’s acquisition of Graphite in 2025.

The launch comes at a time when GitHub is building its own agent-based workflows on top of existing hosting. GitHub Agentic Workflows run agents in GitHub Actions to automate tasks such as issue triage and documentation updates.

Community reaction has been mixed, with skepticism focused more on ownership and data-handling than feature scope. A discussion on Reddit‘s r/github describes Origin as part of a wider land-grab for the developer stack following Cursor’s acquisition by SpaceX.

Developers say they would rather tolerate GitHub‘s downtime than host code on infrastructure ultimately controlled by Elon Musk. Others point to decentralized alternatives such as Forgejo and Codeberg or experimental ATProto based forges like Tangled as more aligned with goals of federation and self-hosting.

Origin appears to strengthen Cursor’s vertically-integrated stack, but heightens concerns about code custody and neutrality that large organizations will need to address before fully adopting the tool.

For teams already invested in Cursor’s editor and agent workflows, Origin may be attractive as a way to reduce context-switching, as it keeps repositories, pull requests, and agent interventions all on one surface while leaving GitHub to handle issues, Actions, and more.

However, Origin’s early beta scope, its reliance on GitHub as source of truth for mirrored projects, and the absence of public projects and built-in CI suggest many organizations will initially treat it as an experiment alongside GitHub rather than as a primary host.