Sign InOpen Brain
VercelEngineering PostOfficial Source

Deploy Cursor Origin repositories with Vercel in public beta

Vercel can now turn Cursor Origin pull requests into previews and merged changes into production deployments, giving agent-built repositories a conventional deploy loop.

Vercel · Aug 17, 2026
Open Source Open MarkdownOpen JSON
Source Summary

Vercel **Pro** teams can connect Cursor Origin repositories. Each pull request creates a **Preview deployment**, while merging triggers a **Production deployment**.

Practical Implication

For agent-driven projects hosted on Origin, connect Vercel at the team, project, new-project, or repository-app level. This restores a familiar review-before-release path without moving the repository.

Agent-Ready Context
Vercel **Pro** teams can connect Cursor Origin repositories. Each pull request creates a **Preview deployment**, while merging triggers a **Production deployment**.

For agent-driven projects hosted on Origin, connect Vercel at the team, project, new-project, or repository-app level. This restores a familiar review-before-release path without moving the repository.

The integration is in **public beta**, Origin remains in **early beta**, and Vercel’s existing private-repository policy applies.
Connected Context · Feed7 Judgment

The integration closes a deployment gap for agent projects that remain on Cursor Origin: pull requests regain preview environments and merges regain automatic production releases. It extends the established review-before-release pattern to a new repository host, but both sides’ beta status makes this an evaluation path rather than evidence of production maturity.

Context Map
infracoding#dev-ux
Uncertainty
The integration is in **public beta**, Origin remains in **early beta**, and Vercel’s existing private-repository policy applies.