Skip to content
Rush Commerce
Tools & Teardowns3 min read

Cursor Origin: keep your git remotes portable

Cursor launched Origin, an agent-scale git forge, the same week GitHub threw errors for seven hours. How to add a remote without handing over your codebase.

Cursor now hosts your code. Origin began rolling out on August 17 in early beta to every paid Cursor plan: repos, pull requests, code browsing, and a two-way GitHub sync. It shipped the same week GitHub spent most of a workday throwing errors. The timing is not an accident, and the correct response is not to switch.

What actually happened

Per Cursor's changelog, Origin is a git forge built for agent scale. Early beta, all paid plans, enterprise admins can opt out. Repos live under a new Codebase tab, you push with the Cursor CLI, and every repo gets pull requests with the timeline, commits, checks and changed files.

The sync is the part worth reading twice. Synced GitHub repos update in real time, and GitHub stays the source of truth for anything that started there — pushes keep going upstream. PR comments move both directions within seconds. Day-one apps: Vercel for preview deployments per PR, plus Depot and Buildkite for CI, both of which run your existing GitHub Actions workflows unchanged.

TechCrunch read it as Cursor capitalizing on GitHub frustration. Fair — GitHub had a seven-hour incident the day Origin landed. This is also Cursor's first major product since SpaceX closed the acquisition.

Why an agent-first git forge matters for your business

Git is the reason you can try this cheaply. A forge is a website wrapped around a protocol you already own. git remote add origin-cursor <url> costs you nothing and takes seconds. Push to both. If Origin's PR review is better for agent-authored diffs — and that is the actual claim — you learn it in a week, on one repo, without a migration.

The lock-in is not the repo. It is everything hanging off it. Your branch protection rules, required checks, Actions secrets, CODEOWNERS, issue templates, deploy webhooks, and the OIDC trust your cloud account extends to your CI. That is the part that does not git push. Before you move a repo, list what is bolted to it. Most teams find eight to fifteen things and stop counting.

Read "source of truth stays GitHub" literally. Cursor is explicit that synced repos keep GitHub authoritative. That is a good design, and it also means Origin does not remove GitHub from your dependency chain. If your goal was fewer upstreams, a mirror is not that.

Beta means beta. Early beta, on a vendor eleven weeks into new ownership, is not where your only copy of production code lives. Try it on a repo you could lose.

Key takeaways

  • Cursor launched Origin on August 17, 2026 in early beta to all paid plans; enterprise admins can opt out
  • Features at launch: repos, pull requests, code browsing, CLI push, and real-time two-way GitHub sync including PR comments
  • Day-one integrations: Vercel preview deployments per PR, Depot and Buildkite for CI running existing GitHub Actions workflows
  • Cursor states GitHub stays the source of truth for synced repos, so Origin adds an upstream rather than replacing one
  • Adding a second git remote is nearly free; the migration cost lives in branch rules, secrets, CODEOWNERS and OIDC trust
  • Inventory what is bolted to a repo before you move it, and keep beta hosting off your only copy

We build systems you can move. Every repo, pipeline and deploy target we hand over is documented, portable, and yours — no vendor holds the only key. See how we build for portability or ask us to audit what your code is actually tied to.

Sources: Cursor Changelog, TechCrunch.

  • #cursor
  • #origin
  • #git
  • #developer-tools
  • #vendor-lock-in
TR

Tommy Rush — Founder, Rush Commerce

Operator turned builder. 15+ years running operations — now shipping the systems businesses run on. More

Get The Rush Report weekly — one email, zero fluff.