摘要
Cursor 发布了自有的代码托管平台 Origin，正向所有付费计划灰度开放（early beta）。Origin 是按「agent 规模」设计的 git 托管服务：建仓库、git push、从其他托管方同步已有仓库，并且可以直接在 Cursor 里评审 Pull Request，包括 agent 自动评审。它与 GitHub 双向同步，远端 ref、merge queue、分支保护和 check run 都会镜像过去，团队不用离开 GitHub 生态就能试用 Origin。Agent 也可以直接 push 到 Origin。首发合作方补齐了周边工具链：Vercel 负责预览部署，Depot 负责 Docker 构建，Buildkite 负责 CI，通过 request-builds 工具和 MCP server 接入。
为什么重要
对工程团队来说，这件事的信号很直接：用得最多的 AI 原生编辑器开始进 GitHub 的核心地盘——托管、code review、CI 集成——说明 coding agent 正在把整条 DevOps 链收进 agent 平台。眼下的价值在于，内置 PR 评审加双向 GitHub 同步，试用成本低，不用放弃 GitHub。需要观察的有四点：beta 稳定性、迁移和锁定风险、与 GitHub 生态的长期对等，以及被 SpaceX 收购后 Cursor 会怎么引导默认设置。
技术细节
| 状态 | early beta，正向全部付费计划推送 |
|---|---|
| 托管 | git 托管；创建仓库、push、从其他托管方同步 |
| 代码评审 | 在 Cursor 内原生评审 PR，包括 agent 自动评审 |
| GitHub 同步 | 双向；镜像 refs、merge queue、分支保护、check runs |
| Agent | agent 可直接 push 到 Origin |
| 应用 | Vercel（预览部署） · Depot（Docker 构建） · Buildkite（CI） |
| 集成机制 | request-builds 工具 + MCP servers |
| 背景 | 发布当天恰逢 GitHub 故障（社区有讨论）；SpaceX 收购完成（2026-08-14，ev-20260814-06）后 Cursor 首个重大基础设施动作 |
| 无仓库启动 | 2026-08-27「Start from scratch」：cloud agents 不再要求连接 SCM；后台自动创建 Origin 仓库 + Create repo（自定义名称、private/internal）；浏览器端口转发实时预览 cloud agent 环境；Vercel 一键发布。Origin 仍为 early beta，无 GA 声明 |
后续更新
2026-08-20 Independent early-beta feedback wave (resolves the 'no independent feedback' watch item; the daily.dev review dated 2026-08-19 and InfoWorld coverage are coverage-gap recoveries first captured by the 2026-08-21 run; aireiter's rollout report dates to 2026-08-17): daily.dev's hands-on test finds the core git workflow functional but 'rough around the edges' — repo hosting, code browsing, PRs, GitHub mirroring and native cloud-agent support work, while public repositories, CI/CD, Issues, Discussions and general polish are missing; their recommendation is to use Origin as a mirror rather than migrating production workflows. InfoWorld: Origin remains far from GitHub's depth in enterprise controls, compliance, auditing and third-party integrations. The Rundown notes the launch landed during a major GitHub outage and that the early beta had performance issues of its own. Implication for the vertical-integration early indication: the repo -> review -> CI -> always-on-agents full-chain story still has CI/CD and public-repo gaps in practice. Recommendation stays WATCH.
2026-08-27 Recovered from index (previous run wrote the update note to index/events.json only): 'Start from scratch': cloud agents no longer require a connected SCM; background Origin repo creation + Create repo (custom name, private/internal); browser port-forwarded live preview of the cloud-agent environment; Vercel publish. Origin still early beta, no GA statement
标签
cursororigincode-hostinggitpull-requestscivercelbuildkitemcpecosystem