Loading post…
CursorAnnouncement
Origin Code Hosting
Summary
Cursor is rolling out Origin, an early-beta code-hosting service for all paid plans, except enterprise organizations whose admins opt out, with repositories, pull requests, code browsing, and GitHub synchronization. Origin-hosted repositories treat Origin as the source of truth: users push through the CLI, while GitHub is not involved; GitHub-synced repositories instead keep GitHub authoritative and mirror changes to Origin in real time. Each repository includes pull-request timelines, commits, checks, file diffs, comments, reviews, and merging, with synced pull requests updating between Cursor and GitHub within seconds. Cursor also places agents alongside code and PRs, allowing them to answer questions, make changes, update pull requests, or push branches, while Vercel, Depot, and Buildkite integrations add preview deployments and CI options.
Context
Origin begins rolling out in early beta to paid-plan users. Enterprise organizations are excluded when their administrators opt out.
Approach / What changed
Origin provides hosted repositories managed through a CLI, alongside synchronized GitHub repositories. It combines code browsing, pull requests, agent actions, access settings, and app integrations in the Cursor interface, with Vercel for preview deployments and Depot or Buildkite for CI.
Takeaways
Origin-hosted repositories use Origin as the source of truth, and pushes go directly to Origin without GitHub in the path.
GitHub-synced repositories retain GitHub as the source of truth, while Origin mirrors updates and synchronizes pull-request comments, reactions, and replies.
Agents can work from repository context to answer code questions, make changes, update pull requests, or push a branch; connected apps add deployments and CI.
FAQ
How do Origin-hosted repositories differ from GitHub-synced repositories?
Origin-hosted repositories receive pushes on Origin, with GitHub outside the workflow. For synced repositories, pushes continue to GitHub and Origin mirrors the result, while users choose which repositories to sync and can disconnect them.
Can pull requests be reviewed and merged from Cursor?
Yes. Repository pull requests show timelines, commits, checks, changed files, diffs, comments, and merge controls. For synced repositories, comments and reactions synchronize between Cursor and GitHub within seconds.
What do the Vercel, Depot, and Buildkite integrations do?
Vercel can create a preview deployment for every pull request, allowing testing and comments before merging to production. Depot and Buildkite run existing GitHub Actions workflows, and Buildkite also runs its native pipelines.
Source and freshness
- Source
- cursor.com
- Published
- Added to Yomu
Summaries are generated from the original by a language model. Check the original before relying on it.
Keep reading
Related reading
The Good Stuff
Paid picks we use ourselves. Links carry a referral code — a subscription through one earns us a commission at no extra cost to you.
The best engineering reads, once a week
One useful email. Unsubscribe anytime.