GitHub's plan for Agents — Kyle Daigle, GitHub
type: NewsArticle
description: GitHub COO Kyle Daigle detailed how the platform is adapting to a 1,400% surge in code shipped by AI agents in 2026, which is straining infrastructure originally built for human-paced development. Daigle addressed challenges including uptime, CI/CD capacity, and open-source maintainer burnout from AI-generated contributions, while outlining GitHub's strategy to integrate agents through existing workflows like Copilot, Actions, and micro-skills. The interview, conducted at Microsoft Build, explored how GitHub aims to preserve the human social contract of software development while becoming the operating layer for autonomous coding agents.
date published: 2026-06-02 16:48:21+00:00
date modified: 2026-06-02 20:28:51.593184+00:00
language: en
is accessible for free: true
article body: *I’m excited to work with Microsoft once again as the presenting sponsors of the AI Engineer World’s Fair!* *We’ll streaming live from* [MS Build](https://build.microsoft.com/)today for a special crossover pod with[our friends at No Priors](https://x.com/saranormous/status/2061681787169017949?s=20)and the one and only**Satya Nadella**. However we did not hold back with this interview - we asked all the burning questions about uptime and Copilot that we know you have in your minds. Lets go!For almost two decades, **GitHub** has been the home of software, where both open source and closed flow, through commits, pull requests, reviews, actions, etc. This ecosystem flourished as open-source maintainers and contributors would continue shipping code for the benefit of the community. However as coding agents began to ship mass quantities of code - **growing 1400% in 2026**, it marked a new era that was both extremely exciting and challenging for GitHub. While these agents help more people ship more projects, they also significantly increase the floor of how much code is shipped, how often it is shipped, how many people commit code, and basically orders of magnitude multiples in every dimension of GitHub infrastructure: Now GitHub inevitably experiences more pressure on their infrastructure which was originally designed around human developers moving at human speed. This has resulted in a very publicly notable uptime story: So it begs the question of whether current systems around code can absorb what AI produces. Can CI/CD keep up when every idea becomes a build? Can open source maintainers survive floods of AI-generated slop contributions? Can GitHub preserve the human social contract of software while becoming the operating layer for agents? Which brings us to the perfect person to answer these questions: **GitHub COO Kyle Daigle. **In this episode, he joins swyx to unpack what happens when AI doesn’t just autocomplete code, but starts changing how companies operate, how…
publisher: Web Pulse
keywords: ai-agents, ai-infrastructure, ai-products, ai-startups, generative-ai
mentions: GitHub
mentions: Kyle Daigle
mentions: Microsoft
mentions: Satya Nadella
mentions: Copilot
mentions: MS Build
mentions: No Priors
mentions: AI Engineer World's Fair
citation: CreativeWork