VS Code: Strongly Recommended Extensions & AI-Powered Debugging

Transcript

Hey there, wonderful developers! Welcome back to another episode of the VS Code podcast. I'm your host, and wow - do we have a fantastic day of development to dive into! March 4th brought us 20 merged pull requests and 30 additional commits, and honestly, this feels like one of those days where everything just clicks into place.

Let's jump right into the main story, because there are some genuinely exciting features landing that I think you're going to love.

First up, Henning just shipped something I've been hoping to see for a while - strongly recommended extensions! You know how sometimes there are extensions that aren't just "nice to have" but are genuinely critical for your workflow? Well, now VS Code can mark extensions as "strongly recommended" and present them in a much more prominent way. The PR added nearly 500 lines of thoughtful code across 13 files, creating this whole new notification system that helps surface those must-have extensions. It's one of those features that sounds simple but required a lot of architectural thinking to get right.

Speaking of making development easier, Paul introduced something super clever - a `/troubleshoot` command that gives you access to debug logs right through the chat interface. This is brilliant because instead of hunting through menus and digging through log files when something goes wrong, you can just type `/troubleshoot` and get the information you need. It's over 680 lines of new functionality, with improved filtering and better presentation of debug information. This is the kind of developer experience improvement that's going to save us all time and frustration.

Martin's been working on something really forward-thinking too - schema-based validation for prompt files. This is laying the groundwork for much better tooling around AI prompt development. We're talking about proper autocompletion, validation, and all the good stuff you'd expect from a modern development environment. It's a hefty change with over 400 lines in the new prompt file attributes system, and it shows how seriously the team is taking AI-first development workflows.

Benjamin has been absolutely on fire with sessions improvements. He shipped multiple PRs today - fixing the Ctrl+W keybinding to actually close sessions like you'd expect, improving modal editor handling with better Escape key behavior, and adding markdown preview support to sessions. These might seem like small touches, but they're the kind of polish that makes the difference between software that works and software that feels great to use.

The inline chat got some love too, with Johannes fixing affordance issues and making sure the Escape key behaves properly. There's even a whole test suite added to make sure these interaction patterns stay solid. It's that attention to user experience details that makes VS Code feel so responsive.

And here's something I find really thoughtful - Don made several improvements to chat session handling, ensuring state updates happen in the right order and avoiding unnecessary model updates. These are the kinds of behind-the-scenes optimizations that make everything feel snappier without you even noticing.

The Git integration got some tweaks too, with Ladislau improving Copilot worktree folder detection. It's a smaller change but shows how the team is constantly refining these integrations to work more seamlessly.

For today's focus, if you're working on VS Code or extensions, definitely check out the new strongly recommended extensions API - this could be huge for extension discoverability. And if you're doing any AI or chat-related work, explore that new `/troubleshoot` command and the prompt file validation improvements. These tools are going to make debugging and development so much more pleasant.

That's a wrap on today's episode! Twenty pull requests, tons of thoughtful improvements, and some genuinely exciting new features. The VS Code team continues to amaze me with their balance of big features and careful polish. Keep coding, keep building amazing things, and I'll catch you tomorrow for another development adventure. Until then, happy coding, everyone!