8月17日早上，Cursor向所有付费用户推出了Origin——它自己的代码托管平台。三个半小时后，GitHub发生了持续近七小时的全球大面积故障。
时间点是巧合，但信号不是。当AI Agent越来越多地承担编码工作，承载代码的基础设施，也到了该重新设计的时候。
Origin不是另一个GitHub
如果只是「又一个代码托管平台」，那根本不值得关注。GitLab、Bitbucket、Gitea……市面上从来不缺。
Origin的不同之处在于它的定位：Agent-native的代码协作环境。它不是在浏览器里给你一个仓库页面，而是把代码托管、PR管理、AI代码审查全部内嵌在Cursor编辑器里。
想象一下这个工作流：你在写代码的同时，AI Agent直接在旁边的面板里帮你审查PR diff，回答问题，应用修改，推送分支——全程不用切换到浏览器。Vercel的预览部署、Depot或Buildkite的CI集成，也都在同一个环境里完成。
这背后是一个正在发生的结构性变化：写代码不再是软件开发的主要瓶颈，代码审查才是。有数据显示，Cursor内部合并的PR中，约35%是由自主AI Agent打开的。当自动生成的代码量越来越大，传统的PR队列越来越像一个调度系统，而不是人类异步讨论的地方。
聪明的「软着陆」策略
Cursor没有上来就喊「替代GitHub」。Origin采用了一种非常务实的迁移策略：GitHub镜像。
你可以连接现有的GitHub组织，Origin实时同步你的仓库。推送仍然走GitHub，GitHub依然是权威来源。但PR评论和权限可以双向同步——你在Cursor里评论，GitHub上也能看到；GitHub上有人回复，几秒内就同步到Origin。
这大大降低了团队的试错成本。不用做高风险的全量迁移，不用说服整个公司换平台，先用起来，觉得好再深入。
但明眼人都能看出来：一旦团队的日常代码审查工作流迁移到了Origin，GitHub就会逐渐退化成一个「存储后端」。当使用习惯和协作网络都搬到了新平台，真正的替代就只是时间问题。
这是一个非常经典的「从侧翼包抄」的策略。
明天见。
On the morning of August 17, Cursor rolled out Origin — its own code hosting platform — to all paid users. Three and a half hours later, GitHub suffered a major global outage that lasted nearly seven hours.
The timing was coincidence. The signal wasn't. As AI agents handle more and more coding work, the infrastructure that hosts code is due for a redesign.
Origin Isn't Just Another GitHub
If this were just 'another code hosting platform,' it wouldn't be worth talking about. GitLab, Bitbucket, Gitea — there's no shortage of options.
What makes Origin different is its positioning: an agent-native code collaboration environment. Instead of giving you a repo page in a browser, it embeds code hosting, PR management, and AI code review directly inside the Cursor editor.
Picture the workflow: while you're coding, an AI agent reviews PR diffs in a side panel, answers questions, applies changes, pushes branches — all without switching to a browser. Vercel preview deployments, Depot or Buildkite CI — it all happens in the same environment.
Underneath this is a structural shift already underway: writing code is no longer the main bottleneck in software development. Code review is. By some estimates, roughly 35% of PRs merged inside Cursor are opened by autonomous AI agents. As automatically generated code volume grows, traditional PR queues start looking more like scheduling systems than human discussion threads.
The Smart 'Soft Landing' Strategy
Cursor isn't yelling 'replace GitHub' from the rooftops. Origin uses a very pragmatic migration approach: GitHub mirroring.
You connect your existing GitHub org, and Origin syncs your repos in real time. Pushes still go to GitHub, which remains the source of truth. But PR comments and permissions sync both ways — you comment in Cursor, it shows up on GitHub; someone replies on GitHub, it syncs back to Origin within seconds.
This dramatically lowers the risk for teams to try it. No high-stakes full migration, no convincing the whole company to switch platforms — just use it and go deeper if it works.
But anyone paying attention can see where this leads: once a team's daily code review workflow moves to Origin, GitHub gradually becomes a 'storage backend.' When usage habits and collaboration networks migrate to the new platform, actual replacement is just a matter of time.
It's a classic flanking strategy.
See you tomorrow.
