VS Code: Strongly Recommended Extensions & Troubleshooting Power-Ups
A massive development push with 20 merged PRs and 30 commits focused on improving the extension experience and debugging capabilities. Key highlights include Henning's new "strongly recommended extensions" system and Paul's innovative /troubleshoot command for chat debug logs, plus significant improvements to sessions, inline chat, and modal editor handling.
Duration: PT4M8S
Transcript
Hey there, code crafters! Welcome back to another episode of the VS Code daily developer podcast. I'm your host, and wow - do we have a packed show for you today, March 4th, 2026. The VS Code team has been absolutely crushing it with 20 merged pull requests and 30 additional commits. It's like watching a well-oiled development machine in action!
Let's dive right into today's big story - and honestly, there are several competing for the spotlight. First up, Henning has delivered something really exciting with PR 299040: support for "strongly recommended extensions." Now, you might be thinking, "We already have recommended extensions, right?" Well, this takes it up a notch.
Picture this - you're working on a React project, and instead of just suggesting extensions, VS Code can now strongly recommend the ones that are absolutely essential for your workflow. It's like having a knowledgeable colleague tap you on the shoulder and say, "Hey, you really should install this one - it'll change your life." The implementation spans 13 files and adds over 450 lines of thoughtful code. What I love about this is how it respects your autonomy while being more assertive about genuinely helpful tools.
But wait, there's more! Paul has introduced something that's going to be a game-changer for debugging: the /troubleshoot command. This PR 299024 adds 680 lines of code across 17 files, and it's all about giving you access to debug logs right from your chat interface. Think about it - when something's going wonky, instead of hunting through menus and settings, you can just type /troubleshoot and get the information you need. It's like having a diagnostic tool built right into your conversation with VS Code.
Now, let's talk about the sessions work that's been happening. Benjamin has been on fire with multiple improvements. There's better Ctrl+W handling to actually close sessions like you'd expect, tweaks to empty message displays, and my personal favorite - markdown preview support in sessions. Sometimes it's these seemingly small quality-of-life improvements that make the biggest difference in your daily workflow.
The inline chat experience got some love too from Johannes. You know that moment when you're using inline chat and accidentally hit Escape and lose everything? Well, now Escape smartly dismisses the affordance without collapsing your selection. It's one of those "finally!" moments that shows how much the team thinks about the developer experience.
I'm also excited about Martin's work on schema-based prompt file validation. This is laying groundwork for better tooling around AI interactions - basically making it easier to write and validate the prompts you use with AI assistants. It's foundational work that's going to pay dividends.
And here's something that might seem tiny but is actually huge - Don's work on chat session option updates. Sometimes the smallest PRs represent the biggest attention to detail. Making sure state updates happen in the right order might not sound glamorous, but it prevents those weird UI glitches that can drive you crazy.
What really strikes me about today's activity is the breadth. We've got extension recommendations, debugging tools, session management, inline chat improvements, git worktree detection tweaks, and modal editor enhancements. It's like watching a symphony orchestra where every section is playing their part perfectly.
For today's focus, if you're an extension author, definitely check out the strongly recommended extensions work - this could change how you think about guiding users to essential tools. And if you're dealing with debugging challenges, keep an eye out for that /troubleshoot command in upcoming releases.
The collaboration energy here is infectious. When you see 20 different improvements all coming together in one day, it reminds you that software development at this scale is really a team sport. Every bug fix, every new feature, every small improvement builds on the work of others.
That's a wrap for today's episode! Keep coding, keep learning, and remember - every line of code is a step forward. We'll catch you tomorrow for another dive into the VS Code development journey. Until then, happy coding!