VS Code 1.141 Adds Agent Session Grid and Worktree Cleanup
Developers can compare long-running agents side by side, reclaim storage from inactive session worktrees and continue selected external conversations inside the editor.
Edited by Tyronne Panaino
Microsoft released Visual Studio Code 1.141 on October 7, 2026 with a set of controls for developers supervising multiple coding-agent sessions. The stable update adds a two-dimensional session grid, guided cleanup for inactive agent worktrees, background-shell visibility, more session filters and continuity for selected conversations created in other apps.
The changes matter to developers using GitHub Copilot or Codex for work that runs across several conversations and isolated worktrees. They turn session management into a visible part of the editor, while leaving the quality, safety and resource efficiency of the underlying agents to be tested in each team's own repositories. GitHub highlighted the grid and cleanup controls again in its October 9 Copilot weekly release.
A grid turns sessions into a monitored workspace
The Agents window in VS Code 1.141 can arrange sessions in horizontal or vertical splits. Developers can resize the panes, maximize one session for focused work and then return to the grid to compare results or watch several long-running tasks.
The session list also gains independent filters for execution environment, agent harness and the application that created a conversation. Microsoft says nested sessions now expose their own unread state and last-modified time, and those indicators persist after the window reloads or VS Code restarts. That is a workflow change rather than evidence that an agent completed its task correctly: the interface makes activity easier to locate, but it does not validate the work produced inside each session.
Cleanup is aware of agent-session state
Agent worktrees can accumulate as isolated sessions create separate checkouts. The new `Chat: Open Worktree Cleanup` command reports the space used by inactive session worktrees, lets users filter by inactivity, shows each worktree's size and allows selected worktrees to be removed.
The cleanup editor can also be configured to act automatically after a session's pull request has merged and to suggest cleanup when inactive storage becomes large. VS Code protects sessions that are active, running, waiting for input or pinned. Cleaning a selected item marks its session done and deletes the worktree; restoring the session later recreates that worktree.
This is narrower than general disk maintenance. The release notes do not quantify typical storage savings, set a universal inactivity threshold or claim that cleanup can replace repository backups. Teams still need to decide when generated files, local-only changes and review artifacts are safe to discard.
Background work and delegated messages become easier to inspect
For Copilot harness sessions, a Background Shells control lists commands that are still running and shows their duration. When output is available, a developer can open the shell entry and follow its stream while the agent continues with other steps.
VS Code also documents more control over messages passed between sessions on the same agent host. An agent can steer an active conversation, queue a separate follow-up, replace a queued message or cancel it before processing starts. Queued messages run in order, and a message can no longer be replaced or cancelled once processing begins. These controls clarify orchestration state, but the official notes provide no measured error rate for delegated work or guarantee that a correction will repair an earlier mistake.
External conversations can move into the Agents window
The release can detect new local conversations from GitHub Copilot CLI and the Copilot app after their first request and display them as external sessions without reloading the Agents window. It also supports continuing a Codex chat started in the ChatGPT app or Codex CLI on the same machine, with its conversation history carried into VS Code.
Only one application can send messages to that Codex chat at a time. If the originating ChatGPT app or Codex CLI session is still open, VS Code shows that the conversation is active elsewhere; the user must close or exit the other client before retrying. The announcement does not establish cross-device continuity, remote migration or compatibility with every external agent provider.
Evidence quality and practical limits
The release is confirmed by Microsoft's detailed stable-release notes and GitHub's official weekly summary. Internal confidence remains medium because both are first-party records of the same product release, with no independent measurements of reliability, storage savings, task quality, security outcomes or enterprise adoption.
For teams evaluating the update, the useful delta is operational: more concurrent sessions can be viewed together, inactive worktrees can be managed with session context, and external conversations can enter the same supervision surface. The next verifiable checkpoints are real-world behavior under large session counts, how cleanup policies perform across active repositories and whether enterprise administrators gain clearer audit data for these multi-session workflows.
Status
Confirmed. Visual Studio Code 1.141 is a stable release, and GitHub's weekly changelog confirms the highlighted Copilot session-management changes. The operational outcomes described above remain unmeasured.
Sources
Update note: Last reviewed 2026-10-10. We will revise this post if Microsoft or GitHub publishes rollout limits, enterprise-control changes or measured operational results.
Sources
Drafted with AI assistance from source briefs; reviewed for citation completeness and label accuracy.