Cursor began rolling out Origin, its own code hosting, in early beta to all paid plans except enterprise orgs whose admins opt out. The initial scope is the essentials described as designed for agent scale: repositories, pull requests, code browsing and GitHub sync, with agent-native features stated as coming.
The part worth reading closely is the source-of-truth rule, because it is stated twice and differently. For Origin-hosted repositories, Origin is the source of truth: pushes land on Origin and GitHub is not in the path. For synced repositories, GitHub remains the source of truth: pushes keep going to GitHub and Origin mirrors the result, with icons distinguishing which repos are hosted and which are synced. Pull requests on synced repos sync both ways — a comment in Cursor posts to GitHub, a reply on GitHub appears in Cursor within seconds — and a review assigned on GitHub can be completed from Cursor. Integrations with Vercel, Depot and Buildkite are available, with Depot and Buildkite running existing GitHub Actions workflows.
Putting code, pull requests and agents in one place is the consolidation tracked in the coding-agent workbench becoming its own product layer, and it follows the boundary Cursor drew in moving agent execution into customer-managed machines. The coding agents hub tracks the forge layer.
This is an early-beta announcement: the agent-native features that justify the phrase agent scale are not shipped yet, and no migration or export path is documented. The condition to watch is whether Origin-hosted repositories keep a plain Git remote for export, because a source of truth without a documented way out is a lock-in decision made at push time.