How VS Code Went from Monthly to Weekly Releases with AI — Harald Kirschner
Harald Kirschner details how the VS Code team transitioned from monthly to weekly releases by fundamentally rebuilding their software development system around AI agents. The focus is not merely on using AI to generate code, but on establishing robust feedback loops, improving CI/CD performance, and implementing quality gates (like automated code review and staged rollouts) to maintain stability at high velocity. Key systemic improvements include achieving a 10x build speed increase with TypeScript Go, automating issue triage from 51 billion daily telemetry events, and making the codebase 'agent-ready' through skills and documentation.
Key takeaways
-
Systemic Change is Key to Velocity
4:32
Achieving high velocity requires evolving the entire software shipping system, not just increasing AI usage. The goal is to make the process of shipping high-quality code faster and more reliably.
-
Code Survival Metrics Improved
1:45
The percentage of agent-written code that successfully gets committed (Code Survival) increased from 55% (using GBD 4.1) to 86% (using Cloud Opus 4.6), demonstrating growing developer trust in AI-generated code.
-
Automated Quality Gates
4:02
The team implemented mandatory AI code review, automated issue triage, and error stack analysis. This process filters 51 billion daily telemetry events into actionable issues and auto-created PRs.
-
Adopting Stage Rollouts
19:05
To derisk the process, VS Code moved away from 'YOLO' (release day 100% rollout) to staged rollouts, monitoring error logs and issues at each step.