AI coding agent 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. Origin 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. The Origin changelog emphasises a narrow feature set rather than a full forge, focusing on repositories, pull requests, code browsing and GitHub sync. According to the docs, developers can use the Origin git guide to clone, push and pull repositories over HTTPS or with the Origin CLI, and browse projects at cursor.com/codebase. Mirrored repositories are pulled from GitHub and kept in sync, while pushes for those projects still land on GitHub, which remains the system of record.
Cursor's marketing and external analysis frame 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 on VentureBeat stresses features such as stacked pull requests and agent aware merge queues, helped by Cursor's acquisition of Graphite in 2025. Cursor staff quoted via ConvNews's summary of a Hacker News thread argue that the goal is to let source control better understand and collaborate with agents, including automatically moving pull requests towards a mergeable state.
A detailed engineer's review on Appwrite's blog notes that Origin is available only to paying customers and flags that enterprise administrators can opt out of the beta. They describe a simple mental model in which teams claim a codebase namespace that becomes part of every repository URL and then perform standard git operations against Origin after CLI authentication. In practice, Origin functions as an additional hosting surface that lives alongside GitHub rather than replacing it, at least in the current release.
The launch comes at a time in which GitHub is building its own agent-based workflows on top of existing hosting. InfoQ recently reported on GitHub Agentic Workflows, which run agents in GitHub Actions to automate tasks such as issue triage and documentation updates, with isolation and constrained execution as design goals. Other InfoQ coverage has looked at GitHub's AgentHQ hub and Copilot CLI, which extend agents into the terminal and CI environment while keeping GitHub as the central repository and collaboration layer.
Timing has drawn as much attention as functionality. An analysis on InfoWorld notes that Origin's beta began rolling out on the same day GitHub experienced a multi hour outage affecting Actions, API requests, git operations and Copilot. TechCrunch's coverage similarly casts the launch as Cursor capitalising on growing frustration with GitHub's reliability while still allowing developers to keep using GitHub in parallel. Commentators on X, including Vaibhav Sisinty, explicitly link the outage and the launch, suggesting that Cursor is offering Origin as a hedge against future disruptions.
Origin has a chance to be the future of this space, with a clean slate and reputation. I pray they do not soil it.
- Hacker News commenter "rvz"
Community reaction has been mixed, with scepticism 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. Another thread on r/cursor notes that Origin is tightly bound to Cursor accounts, reinforcing the sense that it extends the Cursor environment rather than acting as an independent forge. A report on TechTimes points out that Origin shipped without clear data retention or training use policies, raising questions about how hosted code might be used within the SpaceX and xAI ecosystems.
Those concerns echo comments captured in the Hacker News thread summarised by ConvNews, where some developers say they would rather tolerate GitHub's downtime than host code on infrastructure ultimately controlled by Elon Musk. Others point to decentralised 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 questions about code custody and neutrality that large organisations 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 organisations will initially treat it as an experiment alongside GitHub rather than as a primary host.