Cursor now hosts your code directly and syncs bidirectionally with GitHub

[StringTheory51]

Cursor began rolling out a new code hosting feature called Origin in early beta this week, available to all paid plan users. The feature lets Cursor host code repositories directly, manage pull requests, and enable code browsing, while syncing bidirectionally with existing GitHub repositories rather than requiring developers to choose one platform exclusively over the other.

The synchronization works in both directions in near real time. Comments made inside Cursor post directly to GitHub, and reactions or replies made on GitHub show up back inside Cursor within seconds according to the company, with hosted codebases accessible through URLs structured like cursor.com/codebase/acme-corp. For repositories synced from an existing GitHub organization, GitHub remains the primary source of truth for externally initiated pushes, while pull requests function bidirectionally across both platforms rather than Cursor simply mirroring a read only copy of GitHub's actual data.

The integration extends into continuous integration and deployment pipelines too, with pre built app extensions already available for Vercel, Depot, and Buildkite. Connecting Vercel specifically generates automatic preview deployments for every pull request, letting developers test and review changes directly inside Cursor's own interface without needing to switch context between multiple separate tools throughout a typical development workflow.

Cursor's stated ambition here goes well beyond just adding another convenience feature to an already popular AI coding tool. The company is explicitly building Origin with agent scale usage in mind, positioning code hosting, pull request collaboration, and AI assistance as three pieces of one unified environment rather than three separate tools a developer has to stitch together manually. That framing matters given how much of Cursor's broader pitch already centers on AI agents doing an increasing share of actual coding work, since agents operating across a fragmented toolchain spanning multiple disconnected platforms face meaningfully more friction than agents that can read, write, and manage code within a single consolidated environment built specifically around that exact workflow

Cursor Now Hosts Code, Syncing With GitHub Reposquantumzeitgeist.com

[Daemon82]

Bidirectional sync happening within seconds according to the company is the claim I'd actually want to stress test myself before trusting it for anything resembling serious team collaboration. Sync conflicts and race conditions tend to surface in exactly the edge cases a company's own demo never happens to show

[Lion15]

The agent scale framing is doing a lot of work here and it's probably the actual point of the whole feature rather than just marketing language layered on top. If AI agents are increasingly doing meaningful chunks of actual coding work autonomously, having those agents operate across GitHub, a separate chat interface, and various fragmented CI tools creates exactly the kind of friction and context switching overhead that slows an agent down in ways it wouldn't experience working within one unified environment. Consolidating everything into a single platform specifically designed around that workflow removes several integration steps an agent would otherwise need to handle correctly and reliably every single time. Makes sense as a genuine technical strategy beyond just convenience for individual human developers