DEV Community

Cover image for VS Code 1.128 Is Here: Multi-Chat Agent Sessions, Copilot Vision, and OS-Level Shortcuts šŸš€
Muhammad Hamid Raza
Muhammad Hamid Raza

Posted on

VS Code 1.128 Is Here: Multi-Chat Agent Sessions, Copilot Vision, and OS-Level Shortcuts šŸš€

Ever had five different conversations going with an AI assistant, all about the same project, but scattered across five separate tabs? You lose track of which chat had the good idea. You forget which one was just testing something weird. It gets messy fast.

VS Code 1.128 (released July 8, 2026) tackles exactly that problem, along with a few other genuinely useful upgrades. Let's walk through what's new, in plain language. 😊

What Is VS Code 1.128?

VS Code 1.128 is simply the latest update to Visual Studio Code, the free code editor made by Microsoft that millions of developers use every day.

Think of it like a phone getting a software update. Your phone still works the same way, but suddenly you have new camera features or better battery controls. VS Code updates work the same way: same editor you know, but with new tools added on top.

This release focuses heavily on Chat and Agents, the part of VS Code where you talk to an AI to help you write code, debug, or answer questions.

Why This Release Matters

If you use AI chat inside your editor, you already know the small annoyances: switching between chats, losing context, or not being able to attach an image when you need to show a bug visually.

This update directly fixes those friction points. It also adds a shortcut feature that goes beyond the editor itself, and gives teams more control over how AI usage is tracked. In short: less busywork, more focus on actual coding.

Benefits with Real-Life Examples

  • Multiple chats in one Claude session šŸ’¬
    Instead of opening a brand-new session every time you want to try a different approach, you can now keep related chats grouped together. Example: one chat adds a /health endpoint to your Express app, while a peer chat writes tests for it at the same time, and a forked chat tries an alternative way to build the same feature. All three stay organized under one session instead of cluttering your session list.

  • Quick chats without opening a workspace ⚔
    Sometimes you just want to ask a quick question, not open an entire project folder. Now you can start a chat in the Agents window without picking a workspace first. It's like asking a coworker a quick question in the hallway instead of walking them to your desk.

  • Copilot Vision, now generally available šŸ‘€
    You can paste, drag, or drop images and PDFs straight into Chat. Say you have a screenshot of a broken UI layout — you can hand that directly to the agent instead of typing out a long description of what's wrong.

  • Read-only subagent chats (Preview)
    When an agent delegates work to helper subagents, you can now watch their progress in a read-only view without accidentally interrupting them. Useful when you want visibility without micromanaging.

  • Configurable browser tab placement šŸ”§
    You can choose whether integrated browser tabs open in your active editor group, a dedicated side group, or their own window. Small thing, but it keeps your workspace from feeling cluttered.

  • OS-level keyboard shortcuts
    You can now set up shortcuts that trigger VS Code commands even when VS Code isn't the focused window. For example, a cmd+shift+a shortcut on macOS that opens the Agents window instantly, no matter what app you're currently in.

Beginner Approach vs Better Approach: Managing Multiple AI Conversations

Beginner approach: Open a new top-level session every time you want to try a different idea. Result: ten sessions, no idea which one has the code you actually want to keep.

Better approach (as of 1.128): Use multiple chats inside one Claude session. Add a chat, fork from an earlier turn, or run chats in parallel — all while keeping everything grouped under one session that's easy to find later.

This isn't about one method being "wrong." It's just that as your AI usage grows, organized sessions save real time.

Best Tips for Using These New Features

  • āœ… Try forking a chat before starting a totally new session. If an idea works, you keep it. If it doesn't, you didn't lose your original conversation.
  • āœ… Use quick chats for one-off questions. Don't open a whole workspace just to ask something simple.
  • āœ… Turn on OS-level shortcuts sparingly. They're powerful, but pick a key combo that doesn't clash with shortcuts your other apps already use.
  • āœ… If you're on a team, check with your admin about the new OpenTelemetry settings for Copilot — managed settings will always override your personal ones.
  • āš ļø Remember: chats without a workspace only work when the agent host is enabled through the chat.agentHost.enabled setting.

Common Mistakes People Make

  1. Assuming every chat needs its own session. This gets overwhelming fast. The new multi-chat model exists specifically so you don't have to do this anymore.

  2. Forgetting that BYOK (Bring Your Own Key) models don't use utility models by default. If you're using your own key as the main agent and notice chat titles or commit messages aren't generating, it's because chat.byokUtilityModelDefault needs to be set. It's not a bug, it's a default behavior worth knowing about.

  3. Not checking the modelOptions settings when using Custom Endpoint models. If your provider has strict parameter requirements, setting temperature or top_p incorrectly (or forgetting to set them to null when needed) can cause request failures.

  4. Ignoring the difference between sideGroup and window for browser tabs. People often pick one, get annoyed, and don't realize there's a setting to change it.

Wrapping Up

VS Code 1.128 is a solid, practical update. Multi-chat agent sessions make working with Claude in VS Code more organized. Copilot Vision going GA means images and PDFs are now a natural part of your chat workflow. And OS-level shortcuts mean VS Code can be one keypress away, even when it's not in focus.

None of this reinvents the editor. It just removes small annoyances that add up over a normal coding day, which honestly is what good updates should do. šŸ’”

If you found this useful, feel free to share it with a fellow developer who's still juggling ten browser tabs of AI chats. And if you want more practical, no-fluff dev content like this, check out more posts at hamidrazadev.com.

Got a favorite feature from this release? Drop a comment below and let's talk about it! šŸ‘‡

Top comments (0)