VS Code 1.128 landed on July 8, 2026, and it quietly changed the shape of agentic work inside the editor. For most teams, the real question is not "what shipped?" It is "which parts are worth turning on this week without creating a mess?"
Here is the short answer: treat this release as a workflow upgrade, not just a feature drop. The biggest wins come from separating parallel work, keeping quick questions out of repo-bound chats, and setting a few guardrails before developers lean harder on agents.
1. What is the biggest practical change in VS Code 1.128?
The headline feature is multiple chats inside one Claude agent session. Instead of opening separate top-level sessions for every branch of work, you can keep related threads together: implementation in one chat, tests in another, and an alternative approach in a forked chat.
That matters because it matches how engineering work actually happens. A single task often splits into coding, review, validation, and docs. The June Copilot releases were already pushing VS Code toward parallel sessions and clearer agent organization. Version 1.128 tightens that model and makes it easier to keep one task in one place.
2. When should you use multiple chats instead of multiple sessions?
Use multiple chats when the work shares one outcome.
Good examples:
- Main chat writes the feature.
- Peer chat writes tests.
- Forked chat explores a riskier refactor.
Use separate sessions when the work has different owners or different deadlines. That keeps costs, context, and approvals easier to reason about.
A simple team rule works well: if the pull request is the same, start with one session and split into chats only when the task branches.
3. Are quick chats actually useful, or just another surface?
They are useful if your team has a bad habit of polluting project chats with throwaway questions.
VS Code 1.128 now supports chats in the Agents window without selecting a workspace. That means you can ask for a regex, a shell one-liner, or a release-summary explanation without dragging a repo into the conversation history.
This is a small change with real payoff. It keeps workspace chats cleaner, which makes later follow-up prompts more reliable. If a session is supposed to help ship code, keep it about the codebase.
4. What changed with Copilot Vision, and how should teams use it?
On July 1, 2026, GitHub moved Copilot Vision to general availability. In VS Code chat, developers can now attach JPEG, PNG, GIF, WebP, and PDF files directly to prompts. GitHub says the feature works across VS Code chat, GitHub.com chat, and Copilot CLI, and it is available on all Copilot plans.
The practical use case is not "show the AI a random screenshot." It is tighter review loops:
- attach a bug screenshot plus the related component file
- attach a design diff plus the CSS or TSX that needs alignment
- attach a PDF spec and ask the agent to map it to tasks
If you enable this for a team, document what is safe to upload. GitHub notes that image and PDF attachments for Copilot Business and Enterprise are retained for about 24 hours to provide the service. That is fine for many teams, but it should be a conscious decision.
5. Which editor tweak is worth rolling out immediately?
Set a default for browser tab placement.
The integrated browser is now more central to agent workflows, and the June release cycle also expanded browser-based validation inside VS Code. In 1.128, you can choose whether browser tabs open in the active group, a locked side group, or a separate window.
For most teams, sideGroup is the cleanest default because it stops app previews and docs tabs from taking over the main editor column.
{
"workbench.browser.newTabPlacement": "sideGroup"
}It is a minor setting, but it reduces tab churn fast.
6. Is there one shortcut worth teaching the whole team?
Yes: add a system-wide shortcut for opening the Agents window.
VS Code 1.128 can now register OS-level keybindings that work even when VS Code is not focused. If your team is actively using agents, this removes a surprising amount of friction.
{
"key": "cmd+shift+a",
"command": "workbench.action.openAgentsWindow",
"systemWide": true
}The specific key combo can vary, but the pattern is useful: make the agent entry point feel like part of the operating system, not a buried panel.
7. What guardrails should teams set before broader rollout?
Do three things first.
- Decide when developers should use quick chats versus repo-bound chats.
- Set an opinionated browser-tab placement default.
- Review managed AI settings if your team uses Copilot at work.
Microsoft's enterprise AI settings docs now spell out managed telemetry controls and note that policy beats environment variables and user settings. The same docs also recommend sandboxing or dev containers when agents run with elevated autonomy.
That is the right framing for this release. VS Code is getting better at parallel agent work, but better autonomy only pays off if teams stay clear about context, permissions, and data handling.
Bottom line
If you only adopt one part of this release, make it multi-chat sessions with a lightweight team rule for when to branch. If you adopt two, add quick chats for non-repo questions. Everything else becomes easier once your team stops mixing unrelated prompts, screenshots, and validation steps into one long transcript.
References
- Visual Studio Code 1.128 release notes
- GitHub Copilot in Visual Studio Code, June 2026 releases
- Copilot Vision is generally available
- Manage AI settings in enterprise environments
Image credit: "New desk and project" by AMagill via Flickr / Openverse, licensed CC BY 2.0 ([source](https://www.flickr.com/photos/85473033@N00/2373519184)).