Visual Studio Code 1.141
🎬 Watch The Story of VS Code! VS Code is now on Instagram, follow @vscode.ig for updates, tips, and more. Rewatch GitHub Copilot Day. Visual Studio Code 1.141 Released October 7, 2026 Stable Downloads for 1.141.0 Windows x64 Arm64 macOS Universal Intel Apple silicon Linux .deb .rpm .tar.gz Arm instructions Snap Already installed? Use Check for Updates in VS Code. For upcoming features, use the Insiders build . Release highlights This release makes it easier to manage agent sessions, protect agent workflows, edit columnar text, and work across GitHub Enterprise instances.
Clean up worktree storage : Reclaim disk space from inactive agent session worktrees, on demand or automatically. Cross-platform sandboxing : Limit agent access to files and network resources on Windows, macOS, and Linux with terminal sandboxing. Arrange sessions : Compare and monitor multiple agent sessions side by side in a grid layout. Continue external sessions : Pick up local external Copilot and Codex conversations in VS Code without losing context.
Block pasting : Paste block rows across successive lines from a single cursor. Multiple GitHub Enterprise instances : Sign in to GHE.com and GitHub Enterprise Server accounts from the same VS Code window. Agent loop Copilot harness The Copilot harness adds exciting new agent functionality to VS Code. It's powered by the Copilot SDK, so its behavior and capabilities are consistent with other Copilot products, including the standalone GitHub Copilot app and the Copilot CLI.
To start using the Copilot harness, select it from the harness picker in the chat input. In this release, it might already be the default selection for you. You can continue working as you normally do. The harness runs in a dedicated agent host process based on the Agent Host Protocol (AHP), so you can connect to the same agent session from multiple VS Code windows. Learn how to work with the Copilot harness , or explore the architecture and workflows in the agent host blog post .
If you have feedback or requests, please file an issue . Reclaim storage from inactive worktrees Run Chat: Open Worktree Cleanup to see how much disk space inactive agent session worktrees use and remove the ones you no longer need. Filter sessions by how long they have been inactive, review each worktree's size, and select the worktrees to clean up. The cleanup editor also lets you configure automatic cleanup for sessions with merged pull requests and control whether VS Code suggests cleanup when session storage grows large.
When chat.agentSessions.sessionStorageCleanupSuggestion.enabled Open in VS Code Open in VS Code Insiders is enabled, the Agents window notifies you when enough inactive worktrees accumulate or they use enough disk space to make cleanup worthwhile. Cleaning up marks the selected sessions as done and deletes their worktrees. You can restore a session later to recreate its worktree. Active, running, needs-input, and pinned sessions are protected from cleanup.
Keep track of background shells When the agent runs a command in the background, it keeps working on other steps while the command runs. In Copilot harness sessions, a Background Shells pill above the chat input lists the shells that are still running, in both the Agents window and the editor window. Select the pill to see each shell's command and how long it has been running, and select a shell to watch its output stream as the command runs, if output is available.
A shell leaves the list when its command finishes. More control for agent-triggered messages When agents delegate work across conversations, they can adjust the delegated task as requirements change instead of waiting for the other session to finish. The send_message tool supports these actions between sessions and nested sessions on the same agent host: Steer an active conversation with a correction. Queue a follow-up as a separate turn.
Replace a queued message while preserving its place in the queue. Cancel a queued message before processing begins. Queued messages run in order. After a message starts processing, it can no longer be replaced or cancelled. Agent UX Arrange sessions in a grid Compare results, monitor long-running tasks, or work across related conversations without repeatedly switching between sessions. Like in the editor window, the two-dimensional session grid in the Agents window lets you drag sessions into horizontal or vertical splits and resize the panes.
Maximize a session when you need to focus, then return to the grid to continue working across conversations. Compact layout density Setting : window.density.layout Open in VS Code Open in VS Code Insiders Fit more content in the Agents window with the Compact layout density. Compact density uses a shorter title bar, removes the gaps between workbench parts, and reduces pane spacing. By default, the Agents window follows the user-level window.density.layout Open in VS Code Open in VS Code Insiders setting, which also applies to editor windows.
To set a different density for the Agents window only, open it and choose View > Layout Density . The density of editor windows remains unchanged. Additional session-filtering options Focus your sessions list on the work you care about. Open Filter Sessions to filter independently by: Environment : Where the session runs, such as locally, in the cloud, or on a remote host. Harness : Which agent harness the session uses.
Created In : Which application created the session, such as VS Code, Copilot CLI, or the Copilot app. The menu also brings together ordering, grouping, Show Done , and Created Externally controls. Track activity across nested sessions Nested sessions let you split related work across separate conversations. In the Agents window, each nested session shows its unread status and last-modified time, helping you find recent activity and conversations that need your attention without opening them individually.
Status is tracked independently for each conversation: Opening a nested session marks only that conversation as read. An unread nested session does not make the main session appear unread. The last-modified time reflects activity in that conversation, not activity in the main session or another nested session. Read status and last-modified times persist when you reload the window or restart VS Code. To clear unread status for an entire session tree, right-click the main session and select Mark as Read .
Unrelated sessions are not affected. Simplified new-session controls (Experimental) Settings : sessions.chat.experimental.newSessionComposerLayout Open in VS Code Open in VS Code Insiders , sessions.chat.unifiedWorkspacePicker.enabled Open in VS Code Open in VS Code Insiders (Agents window only) The experimental new-session composer keeps your prompt at the center while making session choices easier to review. Workspace, repository, and harness controls now appear in a collapsible Session Options tray above the chat input.
Getting-started tips now appear in a rounded notice below the chat input, so they no longer separate the session controls from your prompt. Collapse the tray to reduce visual clutter without changing your selections. The composer remembers your choice, adapts labels as the window narrows, and keeps the options expanded when screen reader optimized mode is active. When you use a custom chat background, the tray has an opaque surface to keep its controls readable.
Improved context picker positioning The Add Context picker now opens next to the button that invoked it and closes when you select the button again. This keeps the picker visually connected to the chat input in the editor and Agents windows. Move agent picker in context control (Experimental) Setting : sessions.chat.experimental.agentsPickerInAttachContextMenu Open in VS Code Open in VS Code Insiders (Agents window only) If you prefer to have the Agent picker initially hidden from the chat input to reduce the number of controls, you can configur
The rest of this page is on the live site.