Uploaded June 2026 | Updated September 2026, 1 week ago
Shipping faster sounds great until test gaps, review bottlenecks, and triage backlog scale with it. The VS Code team hit all of that going from monthly to weekly releases, and agents made it work. This session breaks down the real patterns: agent sessions before meetings, conversations that become PRs instead of specs, automated triage across one of GitHub's largest repos, and harnesses that keep quality high when 100+ commits land daily. Concrete workflows you can take back to your team.
Seating for this session is first-come, first-served. Add it to your schedule to plan your day and arrive early to secure a spot.
To learn more, please check out these resources:
* https://aka.ms/build26/BRK204
๐ฆ๐ฝ๐ฒ๐ฎ๐ธ๐ฒ๐ฟ๐:
* Pierce Boggan
* Joshua Spicer
๐ฆ๐ฒ๐๐๐ถ๐ผ๐ป ๐๐ป๐ณ๐ผ๐ฟ๐บ๐ฎ๐๐ถ๐ผ๐ป:
This is one of many sessions from the Microsoft Build 2026 event. View even more sessions on-demand and learn about Microsoft Build at build.microsoft.com
BRK204 | English (US) | Developer tools & frameworks
Breakout | (400) Expert
#MSBuild
Chapters:
0:00 - Shift from monthly to weekly VS Code releases and reasons behind it
00:11:08 - Demonstration of agent updating button color from blue to green using screenshots for validation
00:11:46 - Explanation of agent verification loop ensuring UI changes meet expectations
00:23:01 - Introduction of VSC-Bench as VS Codeโs custom offline evaluation stack
00:24:35 - Transition to discussion on VS Codeโs evolved engineering system
00:31:26 - Duplicate issue detection, semantic matching, and GitHub integration improvements
00:34:47 - Automatic handling of unhandled errors via telemetry and GitHub integration
00:36:00 - Cross-process VS Code bug analysis and AI-generated fixes
00:38:00 - Weekly releases and introduction of staged rollouts for safer updates
Shipping faster sounds great until test gaps, review bottlenecks, and triage backlog scale with it. The VS Code team hit all of that going from monthly to weekly releases, and agents made it work. This session breaks down the real patterns: agent sessions before meetings, conversations that become PRs instead of specs, automated triage across one of GitHub's largest repos, and harnesses that keep quality high when 100+ commits land daily. Concrete workflows you can take back to your team.
Seating for this session is first-come, first-served. Add it to your schedule to plan your day and arrive early to secure a spot.
To learn more, please check out these resources:
* https://aka.ms/build26/BRK204
๐ฆ๐ฝ๐ฒ๐ฎ๐ธ๐ฒ๐ฟ๐:
* Pierce Boggan
* Joshua Spicer
๐ฆ๐ฒ๐๐๐ถ๐ผ๐ป ๐๐ป๐ณ๐ผ๐ฟ๐บ๐ฎ๐๐ถ๐ผ๐ป:
This is one of many sessions from the Microsoft Build 2026 event. View even more sessions on-demand and learn about Microsoft Build at build.microsoft.com
BRK204 | English (US) | Developer tools & frameworks
Breakout | (400) Expert
#MSBuild
Chapters:
0:00 - Shift from monthly to weekly VS Code releases and reasons behind it
00:11:08 - Demonstration of agent updating button color from blue to green using screenshots for validation
00:11:46 - Explanation of agent verification loop ensuring UI changes meet expectations
00:23:01 - Introduction of VSC-Bench as VS Codeโs custom offline evaluation stack
00:24:35 - Transition to discussion on VS Codeโs evolved engineering system
00:31:26 - Duplicate issue detection, semantic matching, and GitHub integration improvements
00:34:47 - Automatic handling of unhandled errors via telemetry and GitHub integration
00:36:00 - Cross-process VS Code bug analysis and AI-generated fixes
00:38:00 - Weekly releases and introduction of staged rollouts for safer updates
