Cursor opens Origin code hosting beta with GitHub mirroring

• Origin is entering early beta on Cursor’s paid plans with repository hosting, pull requests, code browsing, and GitHub sync, which Cursor's beta announcement describes as its initial agent-scale feature set.
• Existing GitHub repositories can live alongside Origin-hosted code, while kevinkern's onboarding capture says GitHub remains the source of truth.
• Pull-request review and agent execution now share the repository surface: the feature inventory lists comments, checks, merges, code edits, PR updates, and branch pushes.
• Vercel can turn Origin pull requests into Preview deployments and merged changes into Production deployments, as vercel_dev's beta announcement explains.

A codebase name now becomes part of every repository URL in Cursor’s Origin changelog. Vercel’s rollout note arrived with a concrete pipeline on day one: PR previews, then production on merge.

Cursor’s initial hosted-repository path runs through a new Codebase tab. The Origin changelog describes a compact flow:

1. Create a repository with +New and name the codebase.
2. Install the Origin CLI.
3. Clone an Origin repository or push an existing local project.

The codebase name becomes the URL namespace, such as cursor.com/codebase/acme-corp. Cursor is launching the beta with the repository primitives first, while saying agent-native features will follow.

GitHub is the bridge into Origin, rather than an all-at-once import. Users connect an account, select an organization and choose individual repositories to sync; the official changelog says a sync can later be disconnected.

Cursor describes the sync as real-time and bidirectional for edits and pull requests. GitHub-origin repositories appear alongside Origin-hosted ones, and the onboarding screen explicitly keeps GitHub as the source of truth. That gives teams a shared repository and review surface without moving canonical data on day one.

Each repository carries a conventional review record, including a timeline, commits, checks, changed files, diffs, comments, reviews, and merges. The agent layer can then answer codebase questions, edit code, update a pull request, and push a branch, according to the Origin feature inventory.

The launch puts three previously separate records in Cursor: repository state, review state, and an agent’s writes to the branch.

Vercel’s public beta lets Pro customers connect an Origin repository through team settings, project settings, or repository apps. Its announcement says pull requests automatically generate Preview deployments, while merges trigger Production deployments.

Cursor also named Buildkite and Depot as initial integrations in its launch thread. Vercel is the first integration with an announced event chain from pull request through production deployment.

The beta’s rollout coincided with a broad GitHub incident. A GitHub incident record logged degraded API Requests, Actions, and Pull Requests; a service alert shared by altryne said the same degradation affected Cursor Automations, Cloud Agents, and Codebase.

Cursor said it was tracking its upstream provider’s recovery.