Cursor

Cursor Origin is Cursor’s git forge — code hosting, pull requests, browse/search, and an origin CLI — not a tab inside the editor. It began rolling out 17 August 2026 as early beta on paid Cursor plans (Pro, Teams, Enterprise). Free accounts cannot store code there.

I mirrored GitHub repositories into Origin and did not switch remotes. That is the product’s own adoption path: GitHub stays the source of truth; Origin copies history, branches, tags, and pull requests; comments sync both ways within seconds; pushes on a mirrored repo still land on GitHub. Detach from GitHub only if you want Origin to own the remote.

Feature parity is not a reason to move. Origin does not bring GitHub Issues, GitHub Actions, or the marketplace. Depot and Buildkite can run existing Actions YAML, but only on Origin-hosted repos — not on GitHub mirrors. Cursor has not published retention, residency, or training-use terms for Origin; the host now sits under SpaceX / SpaceXAI. Treat a mirror as a convenience window until those terms exist and the beta has been through a few GitHub outage weeks.

The loop that actually gets closer to Cursor’s infra is cloud agents on a native Origin repo. Those VMs clone into Cursor’s fleet; GitHub HTTPS is no longer the middle of every clone/push, which matters when many agents hit one repo. Cloud agents already clone GitHub today — Origin is not required. Local Cursor agents already have the working tree on disk, so Origin vs GitHub does nothing for them. GitHub Actions minute caps and cancel-queues are a runner-billing problem; Origin does not fix them while the repo stays mirrored.

Cursor’s published Origin roadmap is one sentence: agent-native features ship soon. The June 2026 Compile pitch (Graphite stacked PRs, merge queues, machine-readable review for parallel agents) is the differentiator they are aiming at — not “we also have a PR tab.” Revisit a remote switch when that layer ships and Origin looks like boring infrastructure, not a research preview.

Grok Bot is Cursor’s always-on teammate — desktop and mobile apps with its own cloud computer, routines, and a weekly usage pool metered on your Cursor account. It is not Grok 4.7 inside the editor; Composer 2.5 and Grok 4.7 remain the in-IDE Cursor Models for coding agents.

Access is included on every paid individual Cursor plan (Pro, Pro+, Ultra) and on self-serve Cursor Teams for all members — no separate Grok Bot subscription and no Premium seat required. Weekly included usage resets; extra work can continue on shared on-demand spend if enabled. Enterprise teams must enable access through their account executive.

A free trial is a usage credit (with a 7-day window), not a paid SKU. Individual SuperGrok, SuperGrok Plus, or SuperGrok Heavy accounts can link for additional Grok Bot usage grants; SuperGrok Lite and team/enterprise SuperGrok tiers do not link.