VS Code: Chat System Evolution and Polish Bonanza

Transcript

Hey there, code crafters! Welcome back to another episode of VS Code - I'm your host, and wow, do we have a fantastic development day to dive into. March 27th, 2026 was absolutely buzzing with activity - 20 merged pull requests and 30 additional commits. The team was clearly in full swing, and the community contributions were just incredible.

Let's jump right into the big story of the day - and honestly, it's all about chat systems getting some serious love. Josh Spicer landed what I can only describe as a monster PR - we're talking 863 lines added, 602 removed, spanning 23 files. This is the kind of change that reshapes how things work under the hood. He completely replaced the group-based chat session customizations API with a simpler, flatter approach called the chat session customization provider API.

Now, I know that sounds super technical, but here's why it's exciting - this is the foundation that's going to make it way easier for extension developers to create custom chat experiences. Instead of wrestling with complex group structures, they can now call a clean, straightforward API to register their customizations. It's like going from assembling IKEA furniture with unclear instructions to having perfectly labeled, intuitive pieces.

Connor Peet also made waves with agent plugin storage improvements. Previously, VS Code was storing plugins in this really internal, hard-to-access way. Connor normalized this to use a proper agent-plugins folder right beside your extensions directory, complete with a clean installed.json file. This might seem like housekeeping, but it's actually huge for tooling integration and making the whole plugin ecosystem more accessible.

The telemetry story is really interesting too - Abhitej John added skills usage telemetry that's going to help the team understand how people are actually using different chat skills. They're being super thoughtful about privacy here, using hashed names and only collecting what's needed to improve the experience.

But you know what I love most about today? The sheer number of polish improvements. We had Yogeshwaran fixing testing icon colors to properly inherit from semantic color tokens, solving those annoying visual inconsistencies. The image preview transparency checkerboard got a beautiful fix using conic gradients instead of overlapping linear gradients - no more triangular artifacts at weird zoom levels!

Justin Chen was on fire with chat UI improvements - fixing thinking content rendering and making tool call confirmation content actually readable by making it larger. These might sound like tiny changes, but they're the difference between a frustrating user experience and one that just flows naturally.

I'm particularly impressed by the bug fix from Copilot - yes, our AI assistant is literally contributing code now - fixing context view positioning in auxiliary windows. When VS Code is running in multiple windows, context menus and code action widgets were showing up in the wrong places. That's fixed now, and it's wild to see AI contributing directly to the codebase.

Megan Rogge tackled chat tips functionality, Isidor Nikolic cleaned up vote down reason code that was no longer needed, and we even got memory leak fixes in the timeline pane from xingsy97. Every single one of these changes makes VS Code more reliable and pleasant to use.

Today's focus should be on testing these chat system changes if you're working with extensions. The new customization provider API is going to open up some really exciting possibilities, but it's behind a kill-switch setting for now, so you'll need to enable it explicitly to experiment.

If you're a theme creator, definitely check out those testing icon color changes - your themes should now have more consistent coloring across the board. And for everyone else, just enjoy the smoother, more polished experience these 20 PRs have created.

That's a wrap on today's VS Code development digest! The momentum is clearly building toward something special, and I can't wait to see where these foundation improvements take us. Keep coding, keep creating, and I'll catch you in the next episode!