Cursor launches Origin, a built-in GitHub alternative, as GitHub suffers a major outage

On August 17, GitHub spent much of the day fighting a major outage. By the time the platform had things mostly under control, Cursor had already shipped a built-in alternative. The company announced Origin, a code hosting platform integrated directly into its editor, rolling out in early beta to all users on paid plans that same day, except for enterprise organizations that had opted out.

Origin lives in a new Codebase tab inside Cursor. Every repository gets full pull request support, including diffs, comments, and merging, without requiring users to leave the editor. Since code, PRs, and agents now sit in the same place, users can ask Cursor questions about a repo they're browsing and have it answer those questions, make changes, or push a new branch directly. This tight integration aims to streamline the development workflow by keeping everything within a single interface.

Origin is not a full GitHub replacement, at least not yet. Existing GitHub repositories can sync into Cursor, with GitHub remaining the "source of truth" and pushes from Cursor being routed back to it. Synced repos and PRs update in both directions in real time, ensuring consistency across platforms. Cursor is also building out an app ecosystem for Origin, with integrations for Vercel, Depot, and Buildkite already live for previews and continuous integration, including support for existing GitHub Actions workflows.

Product launches like this are typically locked in weeks ahead of time, from blog assets to staged beta rollouts, so the overlap with GitHub's outage could be coincidental rather than a direct response to it. However, the timing may still give Cursor a strategic advantage, as developers frustrated by the outage might explore alternatives. Whether Origin will evolve into a full competitor to GitHub remains to be seen, but its initial feature set and ecosystem integrations suggest a serious long-term play.