GitHub’s COO Explains Why AI Hasn’t Replaced Developers (28 min)
ai-driven-innovation-economy
ai-in-skill-development
ai-in-workforce-disruption
- Release date: 2026-06-17
- Listen on Spotify: Open episode
- Episode description:
Last year, there were 1 billion commits on GitHub. This year, Kyle Daigle expects that number to exceed 14 billion, a two-component explosion caused by more humans—and their agents—issuing pull requests. In March alone, 17 million pull requests on GitHub were created by agents.Daigle is the COO of GitHub and Microsoft’s chief marketing officer for developer products. He’s been at GitHub for 13 years, and is paying close attention to how AI is expanding the platform’s user base. Along with agents, legal, sales, and marketing professionals are building apps with the GitHub Copilot app. The line between developer and non-developer is disappearing.On this episode of AI & I, guest host Mike Taylor sat down with Daigle at Microsoft Build to discuss how GitHub is building infrastructure for an agent-native world: agentic code review, model routers that automatically select the right model for the task, and a philosophy that the most durable advantage in this market is developer choice.If you found this episode interesting, please like, subscribe, comment, and share!Want even more?To hear more from Mike Taylor:Subscribe to Every: https://every.to/subscribeFollow him on X: https://x.com/hammer_mtTimestamps for YouTube:00:00:52: Introduction00:03:27: The agentic PR flood00:04:33: GitHub's approach to helping open-source maintainers manage the surge00:06:15: What 14 billion commits means for code quality00:08:03: Moving from per-seat licensing to usage-based pricing00:09:45: Kyle's dual role as GitHub COO and Microsoft's chief marketing officer for developers00:13:03: Developer choice as competitive moat00:14:57: How to balance dogfooding your own tools with staying honest about the competition00:19:45: Hill climbing, frontier tuning, and solving the model-routing problem00:24:45: Kyle's agentic communication hackLinks to resources mentioned in the episode:Kyle Daigle on X: https://x.com/kdaigleMike Taylor on Every: https://every.to/@mike_2114Mike’s piece on building an AI version of Kyle Daigle: https://every.to/also-true-for-humans/i-interviewed-an-ai-version-of-github-s-coo-then-spoke-to-the-real-oneGitHub Copilot: https://github.com/features/copilot
Summary
- 👥 Democratizing Development: AI tools like Copilot are expanding who counts as a developer to include knowledge workers building personal apps.
- 🌊 PR Flood Management: Agent-generated pull requests are exploding, requiring new review and maintainer control tools to prevent maintainer burnout.
- 💰 Pricing Model Evolution: 24/7 agent activity is pushing platforms toward usage-based pricing while protecting core free experiences.
- 🔄 Multi-Model Strategy: GitHub emphasizes developer choice by supporting models from OpenAI, Anthropic, Google and its own while avoiding lock-in.
- 🧠 Personal AI Loops: Leaders are using private AI clones for self-improvement feedback on communication and decision-making.
Insights
- How is the definition of a ‘developer’ expanding beyond traditional coders to include knowledge workers using AI tools?
- Time: 1:26 – 3:09
- Answer: Kyle Daigle discusses how GitHub Copilot is now used by legal, finance, and other non-developer teams to build apps, shifting product roadmaps to support casual builders alongside professional devs. This democratizes software creation but requires new on-ramps like the Copilot app.
- What tools and controls can help open source maintainers survive the flood of AI-generated pull requests?
- Time: 3:26 – 5:46
- Answer: With 17 million agent-created PRs in March alone, maintainers face overwhelming volume; GitHub is building agentic code review and merge features while giving maintainers granular controls over acceptance without imposing standards.
- Will AI agents force a shift from freemium to usage-based pricing models in developer platforms?
- How can AI agents create powerful personal self-improvement loops by analyzing your own writing and communications?