VS Code: Chat Commands Get Smarter & Terminal Magic
A significant day for VS Code with 10 merged pull requests and 16 commits focusing heavily on chat functionality improvements and terminal enhancements. Tyler Leonhardt led the charge with major chat slash command updates for GitHub Copilot integration, while Alexandru Dima delivered substantial terminal output capture fixes and sandbox improvements.
Duration: PT4M5S
Transcript
Hey there, developers! Welcome back to another episode of the VS Code podcast. I'm your host, and wow, do we have a packed show for you today. March 23rd brought us some seriously impressive updates that are going to make your coding life so much smoother.
Let's dive right into the big story of the day - chat commands just got a whole lot smarter! Tyler Leonhardt dropped a fantastic PR that's all about making slash commands work better across different AI providers. You know those handy commands like `/clear`, `/fork`, and `/debug`? Well, they were being a bit picky about which chat sessions they'd work with. Tyler realized that these silent commands aren't really attachments - they're just another way to invoke functionality. So he refactored the whole system to let these commands flow through even when certain prompt attachment features aren't available.
The coolest part? Claude users are now getting access to more slash commands, including `/clear`, `/fork`, `/debug`, and `/models`. It's one of those changes that seems simple on the surface but required some really thoughtful architecture work underneath.
Speaking of thoughtful work, we had some fantastic terminal improvements land today. Alexandru Dima has been on an absolute roll with terminal enhancements. One of the standout fixes tackles something that's been bugging developers - when you run commands through chat tools, sometimes the command echo and shell prompts would leak into your output. Alexandru added smart stripping logic that can tell the difference between real command output and all that shell noise. It's particularly clever because it handles different prompt formats across operating systems.
But that's not all from the terminal front! Anthony Kim fixed a really specific but important issue with kitty keyboard protocol and Fish shell. If you're using those together, VS Code wasn't properly intercepting certain meta key commands. Now it checks for active kitty keyboard protocol before letting xterm.js handle the keys. It's one of those fixes that affects a specific setup, but when it hits, it really makes a difference.
Let me give a shoutout to Peng Lyu who tackled some UI polish work. There were a couple of image carousel fixes - one for better position detection and another for handling different data types. These might seem like small changes, but they're exactly the kind of attention to detail that makes VS Code feel so polished.
And here's something that caught my eye - we got a sessions cleanup from Lszomoru that removed code that's no longer needed since checkpoints are now linked. I love seeing these kinds of commits because they show the codebase is actively maintained and simplified when possible. Technical debt gets paid down, and the code stays clean.
There were also some nice quality-of-life fixes, like reducing log spam from duplicate agent skill names, and fixing enter key behavior in the integrated browser. These are the kinds of improvements that you might not notice directly, but they make everything feel more responsive and clean.
Today's Focus: If you're working with chat features in VS Code, this is a great time to explore those slash commands, especially if you're using different AI providers. The expanded command availability means you can streamline your workflow even more. And if you're doing terminal-heavy work, you should notice cleaner output from automated commands.
For those of you contributing to VS Code or working on similar projects, there's a great lesson here about the importance of cross-platform compatibility. So many of today's fixes involved making sure features work consistently across different shells, operating systems, and configurations.
That's a wrap for today's episode! The VS Code team continues to impress with both big architectural improvements and careful attention to user experience details. Keep coding, keep experimenting, and I'll catch you tomorrow with more updates from the world of VS Code development. Until then, happy coding!