Cursor launches Origin, a GitHub alternative built into the editor
Cursor's new Git host lives inside the editor: pull request review, code search, and two-way GitHub sync, all without leaving the app. It shipped 3.5 hours before GitHub's own 7-hour, 47-minute global outage.
Cursor built its own Git host into the editor. It shipped hours before GitHub's global outage.
Cursor launched Origin on August 17, 2026: a Git-hosting platform built directly into its AI coding editor, with its own pull request review, code search, and two-way sync back to GitHub. Roughly three and a half hours later, GitHub itself went down worldwide for 7 hours and 47 minutes. Cursor did not cause the outage and does not claim to, but the coincidence landed in the same week developers were publicly asking whether GitHub still deserves to be the only place code lives.
What Origin actually does
Repos live at cursor.com/codebase/[name]. Inside that view, Origin handles the full pull request workflow: timeline, commits, checks, diffs, comments, and merge, the same jobs a developer currently does on github.com. Code stays browsable and searchable without a second tab.
It is not a silo. Origin syncs two ways with GitHub within seconds, so a push from either side shows up on the other almost immediately. On the deploy side, Cursor has wired in Vercel for preview deploys, plus Depot and Buildkite, both of which can run a project's existing GitHub Actions workflows without a rewrite.
Built for agents, not just humans
Cursor calls Origin "agent native," built for what it describes as "agent scale." The pitch: an AI coding agent working inside Cursor can read a codebase, open and update a pull request, and push a branch, all without the editor handing control to a browser tab pointed at GitHub. Every one of those handoffs today is a place an agent-driven workflow can break stride.
GitHub stays the source of truth, for now
Origin is in early beta, open to all paid Cursor plans; enterprise organizations can opt out, and there is no free-tier access yet. At launch, GitHub remains what Cursor calls the "source of truth": Origin is built to interoperate with GitHub, not replace it outright.
One more data point worth having: the launch landed inside an active Hacker News thread, "Ask HN: Alternatives to GitHub," sitting around 643 points and 431 comments the same week. That thread never names Cursor or Origin. It is shared timing and shared mood, not evidence the two are connected.
Why a build studio cares
We push to GitHub every day, for every build here, without treating it as a dependency that could crack. Origin does not change that habit yet. GitHub is still where the code of record lives for us and for most of the industry. But a well-funded editor shipping its own Git host, one that syncs with GitHub instead of replacing it, is a real test of whether single-vendor trust in Git hosting is starting to loosen.
The part we will actually watch is the agent angle. We run coding agents against GitHub repos daily, and every time an agent has to leave the editor to open a pull request somewhere else, that is friction we feel directly. Whether a second Git host per project is worth removing that friction is not something a beta announcement can answer. We will find out once Origin is open enough to run against a real client repo.
Next step: read Cursor's own changelog entry for the full feature list, cross-checked here against reporting from Slashdot, Cryptonomist, NotebookCheck, and The New Stack. If your team is weighing a second Git host against the friction it would remove, write to us at hello@gattyworks.com.