VS Code: Chat Experience Gets a Major Polish
The VS Code team shipped 12 pull requests focused heavily on improving the chat experience, with significant work on question carousels, terminal integration, and diff viewing. Connor Peet and Megan Rogge led the charge with multiple contributions each, while the team also upgraded ripgrep and fixed some critical Mac browser issues.
Duration: PT3M58S
Transcript
Hey there, VS Code enthusiasts! Welcome back to another episode of the VS Code podcast. I'm your host, and wow, do we have a packed day to talk about. January 31st brought us some really exciting updates that show the team is laser-focused on polishing the chat experience.
Let's dive right into the big story of the day - the chat improvements are absolutely everywhere! Karthik led the charge with a significant overhaul of how question carousels work. They switched to a list-style selection for both single and multi-select questions, which sounds simple but involved touching over 600 lines of code. What I love about this change is that it's all about making the interface more intuitive and accessible for users.
Connor Peet was absolutely on fire today with multiple contributions. One of my favorites is the enhancement to compare block diff actions. This isn't just a small tweak - we're talking about adding toggle functionality between inline and side-by-side diff views, plus a new "open in diff editor" action. If you've ever been frustrated trying to review code changes in chat, this is going to feel like a breath of fresh air. The accessibility improvements alone make this a win, with better screen reader support and improved keyboard navigation.
Connor also tackled what they delightfully called "screen cheese" in sensitive file overflow. I had to chuckle at that term, but the fix actually cleaned up a bunch of old height eventing code that was left over from an earlier refactor. It's always satisfying when you can fix bugs and clean up technical debt at the same time.
Megan Rogge brought us some crucial terminal fixes that might seem small but make a huge difference in daily use. The terminal output positioning issue was caused by something pretty subtle - the difference between clearing a buffer and doing a full reset. When you clear the buffer, the cursor stays put, but new content gets written in the wrong spot. The fix was switching to a proper reset that moves the cursor back to where it should be. Sometimes the best fixes are the ones that make you go "oh, of course!"
She also fixed an issue where auto-approved terminal commands were still triggering notifications and sounds. Nobody wants their computer beeping at them for commands they've already said are okay to run automatically. The fix involved adding some defensive guards to prevent race conditions - exactly the kind of attention to detail that makes VS Code feel polished.
One thing I really want to highlight is the collaborative nature of these changes. You can see in the pull requests how team members are building on each other's work, iterating and improving. Connor's follow-up PR that cleaned up the auto-approval state shows this perfectly - taking a good fix and making it even better.
We also got a nice infrastructure upgrade with Raymond bumping ripgrep to version 1.17.0. This might not sound exciting, but ripgrep is the engine that powers VS Code's blazing-fast search, so staying current with updates like this keeps everything running smoothly.
And Kyle fixed some fundamental keyboard shortcuts on Mac browsers - undo, redo, and select all. These are the kinds of issues that can drive you absolutely crazy when they're broken, but when they work, you never think about them.
For today's focus, if you're using VS Code's chat features regularly, take some time to explore these new diff viewing options. The ability to toggle between inline and side-by-side views, plus opening diffs in the full editor, could really change how you review and work with code suggestions from chat.
That's a wrap on today's episode! The VS Code team continues to show that great software comes from sweating the details and listening to user feedback. Keep coding, keep building, and we'll catch you tomorrow for more VS Code adventures!