Don't Rip Out GitHub on Day One — What Cursor Origin's Early Beta Actually Ships

On 2026-08-17, Cursor began rolling out Origin in early beta on all paid plans. Agents already write faster than human review queues can absorb; today Cursor opened the hosting layer itself.

Core takeaway: day-one Origin is not a finished GitHub replacement. The changelog ships repos, pull requests, code browsing, and GitHub sync — essentials “designed for agent scale” — and says agent-native features ship soon. For synced repositories, keep treating GitHub as the source of truth until you deliberately Detach.

Why it matters

Agent workflows bottleneck less on generation and more on review, merge, and release gates. If an agent can open a PR from the IDE but the host is still tuned for human-paced Issues/Actions/permissions, “agent speed” dies in the queue.

Origin tries to pull that queue into Cursor. The same changelog also labels agent-native hosting features as soon. Today is foundation day, not “fully autonomous host-native agents” day.

Three practical shifts land immediately:

1. Code custody becomes a choice — Cursor-hosted repos can sit beside GitHub-synced ones.
2. PR review surfaces dualize — synced-repo PRs sync Cursor ↔ GitHub both ways.
3. Deploy/CI attach via apps — launch mentions Vercel, Depot, and Buildkite.

How it compares

The December 2025 Graphite acquisition explains lineage (review-throughput talent inside Cursor). Graphite continues as its own product per Cursor’s post — do not merge that roadmap into Origin’s day-one checklist. Compile-era commits-per-second demo numbers are absent from the Aug 17 changelog, so this draft does not cite them.

Code / config example

Skip migration theater. Add an observability remote first. URLs depend on your Codebase name — placeholders only:

# 1) Assume GitHub is already `origin`
git remote -v

# 2) Add the Origin remote from the repo’s CLI instructions
git remote add origin-cursor <ORIGIN_REMOTE_URL>

# 3) Dual-push only an experiment branch — leave main alone
git push -u origin-cursor experiment/origin-smoke

# 4) If you use sync/mirror: docs keep GitHub as SoT for pushes
#    Detach is Danger Zone — SoT flips to Origin

A short team checklist to paste into the repo:

# Origin early-beta checklist
- [ ] Confirm paid plan / Enterprise admin opt-out policy
- [ ] Sync one non-critical repo only (not the prod monorepo)
- [ ] Verify Issues, Actions, and secrets still live on GitHub
- [ ] Connect Vercel/Depot/Buildkite only from the Apps tab if needed
- [ ] Detach only with explicit approval

I hit a wall the first time I enabled sync and hunted for Actions logs inside Origin. It felt like a host outage until the mirror docs stated the obvious: GitHub Actions workflows and secrets are not included. After that I stopped expecting Issues/CI to appear on the Origin surface.

Practical use

Recommended order:

1. Enterprise? Check admin opt-out first — changelog: enterprise orgs are included unless admins opt out.
2. Name the Codebase carefully — creating your first repo influences codebase naming in the URL structure. Don’t mix personal sandbox names with company org names.
3. Connect GitHub → pick org → sync selectively — never import everything on day one.
4. Use bi-directional PR sync for review in Cursor — comments/reactions show up within seconds; GitHub-assigned reviews can be reviewed and merged from Cursor.
5. Need deploys? Vercel app — same-day Vercel public beta: Origin PRs get Preview deployments; merge triggers Production. Origin repos follow Vercel’s existing private-repository policy.
6. CI via Depot/Buildkite — changelog says both can run existing GitHub Actions workflows; Buildkite also runs native pipelines. That is not “Actions moved into Origin.”

Detach lives under Settings → General → Danger Zone. It stops sync and makes Origin the source of truth. Your GitHub repository is not deleted. Treat that button as a host cutover, not an “end experiment” toggle.

Senior-engineer perspective

The senior question is not “is Origin cool?” — it is which layer of source-of-truth are you moving?

• Git objects (commits/branches/tags) — included in the mirror; easy to reverse.
• PR metadata — bi-directional sync; good place to shift review UX into Cursor.
• Issues / Actions secrets / platform metadata — excluded from the mirror; this is where ops weight actually lives.
• Agent-native host features — soon. Do not treat a roadmap adverb as a shipped capability.

It is tempting to narrate this through the SpaceX close. Keep today’s unit of work smaller: one non-critical synced repo + an explicit SoT table. Detach without that table and next week’s on-call debugs two hosts at once.

Using it in Cursor

1. Open the Codebase tab → +New to create a repo, or connect GitHub sync.
2. Copy CLI install/clone/push instructions from the repo page into your local machine.
3. Use the host icons beside repo names to tell Cursor-hosted vs GitHub-hosted copies apart.
4. If you plan to attach Cloud Agents to an Origin repo, write the current SoT into agent rules/runbooks first.
5. If you only need automated review comments on GitHub PRs, docs note Cursor Review / Bugbot can do that without moving storage — hosting migration is not the only path.

Agent-prompt one-liner:

Origin-synced repo: GitHub remains source of truth for pushes.
Do not Detach. Do not migrate Actions secrets. Open PRs; leave Issues on GitHub.

FAQ

Q. Can we turn off GitHub today?
A. Given early-beta essentials and agent-native features marked soon, a full production cutover is not recommended. Start with sync.

Q. Where are Issues and Actions?
A. Per mirror docs, GitHub Issues and Actions workflows/secrets are not included. Leave them on GitHub.

Q. We’re on Enterprise and see nothing.
A. Admins can opt out. Check admin settings.

Q. Is the Vercel integration GA?
A. Vercel’s side is public beta; Origin is early beta. Preview/Production automation is described for connected Origin PRs/merges.

Q. Do Graphite stacked PRs turn on automatically?
A. Graphite is lineage. Day-one official scope is repos/PRs/browse/sync. Do not assume stacked workflows ship with the beta.

Sources

• Origin Code Hosting · Cursor Changelog (2026-08-17)
• Mirror a GitHub repository · Cursor docs
• Cursor · Origin
• Deploy Cursor Origin repositories with Vercel (public beta)
• Graphite is joining Cursor

Closing

Hosting in the agent era is less about a prettier git UI and more about where SoT, secrets, CI, and review surfaces live. Origin’s early beta opens that choice toward Cursor without telling you to shut GitHub off.

The watch item for the next month is how fast “soon” graduates into shipped agent-native hosting. Until then, default to sync, dual remotes, and no Detach.