VS Code: MCP Magic and UI Polish Galore
The VS Code team shipped 20 pull requests focused heavily on MCP (Model Context Protocol) improvements and UI enhancements. Connor Peet led the charge with major MCP enablement features and UI improvements, while the team tackled everything from macOS terminal fixes to inline completion enhancements.
Duration: PT3M56S
https://podlog.io/listen/vs-code-6ffbd97f/episode/vs-code-mcp-magic-and-ui-polish-galore-4c50abc3
Transcript
Hey there, VS Code enthusiasts! Welcome back to another episode of your favorite daily developer podcast. I'm your host, and wow - do we have a packed show for you today, March 10th, 2026.
The VS Code team absolutely crushed it with 20 merged pull requests and 30 additional commits. And let me tell you, there's a clear theme emerging here - they're really doubling down on making MCP and chat experiences smoother than ever.
Let's dive right into our biggest story of the day. Connor Peet has been absolutely on fire with MCP improvements. First up, he delivered a massive PR that lets you enable and disable MCP plugins just like regular extensions. This isn't just a small tweak - we're talking about over 1,000 lines of code changes across 31 files, introducing a whole new EnablementModel. You can now control plugins at both workspace and global levels, and access these controls right from the marketplace view and chat customizations. It's exactly the kind of user control we love to see.
But Connor wasn't done there! He followed up with another substantial change, moving MCP to use the askquestions UI for elicitations instead of that old quickpick flow. This is such a smart move - it creates a much nicer user experience and adds proper data validation. Sometimes the best improvements are the ones that make complex things feel simple.
Now, here's a story that'll resonate with anyone who's ever battled terminal quirks. Jamie Cansdale tackled a really gnarly macOS bug where multiline terminal commands over 1KB would get corrupted due to PTY buffer issues. The fix is elegant - chunk those writes into 512-byte pieces with tiny pauses between them. It's one of those fixes that'll save countless developers from frustrating debugging sessions without them ever knowing it.
The UI polish continues with some fantastic work from Osvaldo Ortega. They fixed file icon rendering in sessions context attachments - no more generic file icons everywhere! Now you'll see proper TypeScript, Python, and other language-specific icons just like you'd expect. Plus, they added a "Group by Repository" toggle for the sessions list, giving you more control over how you organize your work.
Johannes Rieken delivered some smart improvements to quick suggestions, making them play nicely with inline completions. The logic is beautifully simple - suppress suggestions when inline completions are active, but allow them when inline providers don't have results. It's these kinds of thoughtful interactions that make VS Code feel so polished.
We also saw some interesting architectural cleanup from Matt Bierner, moving chat model change listeners to a more logical home on the chat service. It might sound boring, but this kind of code organization work is what keeps VS Code maintainable as it grows.
There was a bit of drama with the debug panel changes - a big OpenTelemetry data source feature got merged and then reverted the same day. That's totally normal in software development, and honestly, it shows the team's commitment to stability over rushing features.
For today's focus, if you're working with MCP or chat features, definitely explore those new enablement controls Connor added. And if you're on macOS and do a lot of terminal work, that buffer fix should make your multiline commands much more reliable.
The energy around VS Code development continues to be incredible. Seeing contributors like Connor, Jamie, Osvaldo, and the whole team iterate so quickly while maintaining quality is genuinely inspiring. Whether you're building extensions, customizing your setup, or just coding away, you're part of this amazing ecosystem.
That's a wrap on today's episode! Tomorrow we'll be back with more VS Code goodness. Until then, keep coding, keep learning, and remember - every commit is a step forward. Catch you next time!