Visual Studio Code 1.141 is rolling out to stable users with a batch of improvements aimed at the editor’s expanding AI and collaborative workflows. The update leads with a change that addresses a growing annoyance for agent power users: the disk space that abandoned sessions quietly consume. Alongside that, it brings Copilot sandboxing, new session layouts, and better GitHub Enterprise support.
Here’s everything that changed in Visual Studio Code 1.141.
#1 Track dead agent session disk usage
The most notable addition is that VS Code now tracks how much disk space dead agent sessions are wasting. When you work with the editor’s agent features, each conversation can leave behind cached data, and once a session is abandoned that data tends to linger. Over time those leftovers can pile up into a meaningful chunk of storage.
This update gives you visibility into that waste, so you can identify and remove stale sessions instead of guessing. In practice, it means the editor is finally accounting for the footprint of its own AI features rather than letting them accumulate unnoticed.
For users running heavy local-model agent workflows, this is a practical housekeeping tool. It also reflects a broader trend: as editors bake in more autonomous AI agents, managing their side effects—disk, memory, background processes—has become a real concern for developers.
#2 Copilot sandboxing across platforms
GitHub Copilot is now sandboxed across platforms in this release. Sandboxing means the AI assistant runs in an isolated environment, limiting what it can access on your system if something goes wrong. This is primarily a security hardening measure.
By confining Copilot to a sandbox, Microsoft and GitHub reduce the blast radius of any vulnerability in the agent code or in prompts that might trigger risky behavior. It’s part of a wider push to make AI coding assistants safer to run continuously inside your development environment.
The cross-platform scope matters because it ensures the protection isn’t limited to one operating system. Whether you’re on Windows, macOS, or Linux, the same isolation model applies.
For everyday developers, this should mean fewer worries about an always-on assistant reaching beyond its intended scope—without changing how you interact with it day to day.
#3 Session grid layouts
The release also introduces session grid layouts, giving you a different way to organize and browse your agent conversations. Instead of scrolling through a single long list, you can view sessions as a grid, making it easier to spot the one you’re looking for.
This is a quality-of-life improvement for users who accumulate many sessions during a work session. It’s especially useful when you’re juggling multiple agent tasks and need to jump between them quickly.
The grid view complements the disk-tracking feature above: as your sessions grow in number and footprint, having a clearer way to see them all becomes more valuable.
#4 Multi-instance GitHub Enterprise logins
Another change lets you log into multiple GitHub Enterprise instances at once. Previously, switching between work and personal GitHub Enterprise accounts often meant logging out and back in. Now you can maintain several authenticated sessions simultaneously.
This matters for developers who work across organizations or manage separate enterprise deployments. It removes a repetitive friction point that came up regularly in team settings.
The addition aligns with VS Code’s broader push to support complex, multi-account development setups without constant re-authentication.
#5 Block pasting
The update also adds block pasting, a feature that changes how you paste content into the editor. Rather than a simple clipboard drop, block pasting handles larger chunks of content more intelligently, preserving structure as you move it around.
For people who frequently copy code, markdown, or formatted text between files, this can make editing feel smoother and less error-prone.
What This Means for You
Taken together, these changes target the workflow of developers who lean heavily on AI agents and multi-account setups. The disk tracking and session grid directly address the mess that powerful features can leave behind, while Copilot sandboxing adds a security layer you may not notice but will appreciate.
The GitHub Enterprise and block-pasting tweaks are smaller, but they remove real friction for the users who hit them regularly. If you work in a team across multiple GitHub Enterprise accounts, the multi-login support alone may be worth the update.
How to Get Visual Studio Code 1.141
You can update to Visual Studio Code 1.141 through the editor’s built-in update prompt, which should appear automatically. If it doesn’t, you can download the latest installer from the official VS Code website.
Enterprise admins distributing via WSUS or channel-based installs should check their update pipeline to ensure the new build is available to managed machines.
Source: Neowin
Over to you: Which of these Visual Studio Code 1.141 features will you reach for first—the dead-agent disk tracker or Copilot sandboxing?
