LecturaInvestigaciónRadarMarco de inversión
Iniciar sesión / Registrarse
← Volver a la lectura
NoticiasTema · GitHubMaterial3 min de lecturaEditorial de DisconfirmAI

GitHub COO Kyle Daigle: Agent Traffic Patterns Upend Scaling Assumptions, Code Verification Becomes the Next Bottleneck

GitHub executives at the Universe 2026 conference explained why services that previously ran stably unexpectedly crashed in the Agent era, and why verification, rather than generation, will become the new constraint facing the platform.

2026-10-29 21:30 GMT+8

At the GitHub Universe 2026 conference held in San Francisco, GitHub Chief Operating Officer Kyle Daigle and Microsoft CoreAI Executive Vice President Jay Parikh (now leading GitHub) faced a sharp question: with the competitive platform Entire, founded by former CEO Thomas Dohmke, just launching, does GitHub need to worry about being replaced? Daigle’s answer was: the world does not need a new GitHub; it needs GitHub to evolve for the Agent era. However, the technical rationale supporting this judgment is worth examining more closely than the slogan itself.

Daigle explained that GitHub began experiencing a series of unexpected failures starting this summer—services designed for human developer traffic patterns, which had run stably for a long time, suddenly crashed. He attributed this not to insufficient capacity, but to fundamental differences in behavior patterns: Agents operate in ways completely different from humans. Some services scaled well under human usage but exhibited failure points the team had not anticipated under concurrent Agent access. He explicitly stated that simply increasing core counts and horizontal scaling is no longer sufficient; core services themselves must be rewritten because the behavioral differences are too great.

Parikh added that the current growth rate makes incremental optimization meaningless. With extensive experience scaling infrastructure at Facebook and Akamai, he judged that achieving five to ten percent improvements now only buys one or two weeks. Therefore, GitHub decided to completely rewrite its core services rather than merely adding capacity.

Iniciar sesión / Registrarse
LecturaInvestigaciónRadarMarco de inversión

The specific architectural responses include two levels. First, separating compute from storage within the Git infrastructure allows both to scale independently according to their respective needs. Parikh explained that compute and storage load variation patterns differ based on traffic type, time of day, user identity, and product form; separation enables independent optimization. Second, migrating from GitHub’s own data centers to Azure provides elastic capacity, geographic flexibility, and redundancy—features fixed facilities cannot offer. As of early October, the migration was approximately 60% complete.

However, Daigle believes the true new constraint lies not in generation, but in verification. When five or ten Agents simultaneously submit code to a repository, running full builds for every submission is neither desirable nor necessary. He proposed several possible directions for response: signing locally executed builds and submitting them alongside the Agent’s work, selecting smaller sets of relevant tests, and exploring proof-driven development methods. He emphasized that the correct combination of testing, evaluation, and real-time verification depends on the specific application scenario—automakers will not let Agents autonomously check whether brake calipers are engaged.

In terms of competitive narrative, Parikh positioned GitHub as a platform company: providing a complete workflow while also offering primitives that can be used independently, allowing enterprises to retain choice. He explicitly stated that GitHub has both products and platforms, whereas much of the current competition consists of single-product tools. Daigle analogized the current moment to the end of the zero-interest-rate era—when numerous sophisticated but extremely narrow developer tools emerged, and ultimately many teams joined GitHub. This analogy implies that the Agent era will similarly experience tool fragmentation, but platform integration remains the final direction.

It should be noted that all of the above represents self-assessment and strategic narrative from GitHub’s leadership. Dohmke’s response directly questioned the premise: entrusting the future of software development to a single large tech company is itself a problem. Daigle’s description of Agent behavioral patterns causing unexpected failures is an attributive statement; while GitHub has published a public post-mortem of the August outage, this article did not read the specific technical details of that report. The argument regarding the verification bottleneck remains a directional judgment at present, with no deployed solutions yet available to prove its feasibility.

Fuentes

  • thenewstack.ioThe New Stack↗
  • geekwire.comGeekWire↗
Tema

GitHub

GitHub 正在重构其 Git 基础设施,以应对人工智能代理(AI Agents)带来的流量激增。随着开发者与 AI 代理并发工作,传统的“仓库级锁”机制成为瓶颈,导致写入吞吐量受限。GitHub 首席运营官 Kyle Daigle 指出…

6 pasos1 piezasActualizado 2026-10-31 21:33

Cómo llegó hasta aquí

  1. 2025-08-01GitHub 开始将代码库副本迁移至 Azure Central US 区域,以缓解本地数据中心容量限制。github.blog ↗
  2. 2026-09-01数据显示,2026年9月 GitHub 上由开发者和代理产生的提交数达 73.8 亿次,是去年同期的五倍以上;Git 总活动量翻倍至每月 4733 亿事件。github.blog ↗
  3. 2026-10-06GitHub 工程博客发布文章《Building Git infrastructure for agent-scale development》,详细阐述为支持代理规模开发而进行的架构重建计划。github.blog ↗

Lo que aún está pendiente

  • GitHub 剩余 0.00001% 的高负载仓库在完成最终架构调整后,是否会出现性能回归或稳定性问题?
  • 竞争对手 Entire 及其背后的开源社区能否真正吸引足够多的开发者离开 GitHub 的中心化生态?
  • 随着代理数量进一步增长,GitHub 提出的“验证成为新瓶颈”这一观点是否会引发对代码审查和合并流程的新一轮工具链革命?
Leer el tema completo →
Continuar investigando →