🔶 版本控制将如何为 Agent 爆发而演进
英文标题：🔶 How version control will evolve for the agent boom
随着 AI Agent 成为代码生产的主力，版本控制需捕获 Agent 会话日志并将其作为代码库的语义记忆层，以消除重复错误、提升准确性与效率、降低 token 消耗。同时，Git 托管必须回归去中心化设计，以支撑 Agent 的大规模并行开发并实现数字主权。这将催生人与 Agent 全天候协作、以机器速度交付软件的新一代平台。
50.6 KB
中文
开发者开始采用 Git 已经过去了二十多年。Git 是当今最流行的版本控制系统，并且还会继续存在至少二十年。问题不在于 Git 能否依靠其强大的生态锁定而存活，而在于我们如何扩展、重构和演进 Git 托管，以迎接 AI Agent 成为代码主要生产者的世界。
捕获软件的灵魂
Git 捕获代码仓库中纯文本文件所写的内容。简单来说，它存储代码行和提交消息，创建随时间变化的记录。但随着 Agent 让代码变得日益丰富，代码背后 "why" 的上下文变得至关重要：Agent 会话及其提示词、工具调用、检查点和决策。这些揭示了开发者的意图，讲述了软件是如何被构建的故事。
我们的假设很简单：会话日志现在是软件开发中最重要的产物，应该与代码本身一起存储在代码仓库中。借助这个语义记忆层，Agent 可以避免重复错误，从而实现更高的准确率、提升生产力并降低 token 消耗。而人类可以更容易地理解和验证所构建的内容及其原因，提供了溯源层，从而大大缩短审查周期。
有了这个在代码仓库中保留的新语义层，人类团队和 Agent 集群可以并行协作构建，不会相互覆盖、冲突或丢失理解。
让 Git 回归最初的承诺
就其设计而言，Git 一直是去中心化的。每个克隆体都包含仓库及其完整历史的完整副本，允许软件在许多主机上复制，而不是由单一服务器控制。但在实践中，Git 托管平台很大程度上将开发者导向了中心化系统。在 Agent 出现之前，这尚可维持。
在一个庞大的 Agent 集群以惊人的速度和并行度编码的世界里，继续通过这种中心化平台路由一切将导致速率限制、宕机、Agent 变慢，并从根本上制约软件开发生命周期。Git 托管必须演进来兑现它最初的承诺：一个由众多主机组成的分布式网络，而不是将全世界的软件存储在一处的系统。仓库应尽可能多地存在，这不仅提高了可用性和弹性，还使 Agent 能够以大规模、更本地化、更有弹性和可扩展的访问模式进行查询、同步和操作。
这也提供了数字主权的明显好处。借助去中心化架构，开发者与组织可以在区域内托管、复制和存储代码，实现数据驻留，同时仍然参与更广泛的全球分布式协作网络。
Agent 的合奏
Agent 已成为新的编码者，随着这一转变，软件开发者将需要比以往更深入的工程判断力。我们现在的角色是将我们的想法注入一个需要保持同步的 Agent 合奏中。在这些新的软件开发循环中，Git 仍将是代码的真实来源。它将捕获溯源、协调 Agent 工作，并在去中心化网络上运行。由此，我们将创建真正能够让 Agent 与人类全天候协作、以机器速度构建和交付软件的平台。
English / 原文
It's been over twenty years since developers started adopting Git. It's by far the most popular version control system today. And, it will be around for another 20 years to come. The question is not if Git survives through the sheer weight of its ecosystem lock-in. The question is how we can expand, rewire, and evolve Git hosting for a world where AI agents are the primary producers of code.
Capturing the Soul of Software
Git captures what was written in plain text files in a repository. In simple terms, it stores lines of code with commit messages, creating a record of what changed over time. But as code becomes increasingly abundant through agents, the context behind "why" the code was written is becoming vital: the agent sessions with their prompts, tool calls, checkpoints, and decisions. They all reveal the intent of the developer and tell the story of how a piece of software was built.
Our hypothesis is simple: session logs are now the most important artifact in software development, and should be stored alongside the code itself in the repository. With this semantic memory layer, agents can stop repeating mistakes, which enables higher accuracy, increases productivity, and decreases token spend. And humans can more easily understand and verify what was built and why, providing a provenance layer that leads to far faster review periods.
With this new semantic layer preserved in the repository, groups of humans and fleets of agents can collaborate and build together in parallel without overwriting, colliding, or losing understanding.
Returning Git to Its Original Promise
By design, Git was always meant to be decentralized. Every clone contains a complete copy of the repository and its history, allowing software to be replicated across many hosts rather than controlled by a single server. But in practice, Git hosting platforms have largely routed developers into centralized systems. This was sustainable until agents came along.
In a world where large fleets of agents are coding with incredible speed and parallelization, continuing to route everything through such centralized platforms will lead to rate limiting, outages, slower agents, and a fundamentally constrained software development lifecycle. Git hosting must evolve to meet its original promise: a distributed network of many hosts, not a system where the world's software is stored in a single location. Repositories should exist in as many places as possible, allowing for not only higher availability and resilience, but also enabling agents to query, synchronize, and operate against them at massive scale and more local, resilient, and scalable access patterns.
This also provides the clear benefit of digital sovereignty. With a decentralized architecture, developers and organizations can host, replicate, and store their code with data residency in-region while still participating in a broader, globally distributed collaborative network.
Orchestra of Agents
Agents have become the new coders, and with this shift, software developers will need deeper engineering judgment than ever before. Our role is now to stream our ideas into an orchestra of agents that needs to be kept in sync. In these new software development loops, Git will remain the source of truth for code. It will capture provenance, coordinate agent work, and operate across a decentralized network. With that, we will create platforms that truly enable agents and humans to collaborate, build, and ship software around the clock at machine speed.