Visual Studio Code 1.142
Join VS Code at Microsoft Ignite or catch the sessions online. A year of VS Code, wrapped. Explore the highlights. Visual Studio Code 1.142 Released October 14, 2026 Stable Downloads for 1.142.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 adds shared canvases for agent workflows, lets you move chats without losing context, expands the Markdown editor, and gives administrators more control over agent permissions.
Canvases (Preview) : Collaborate with agents beyond chat using visual and interactive canvases. Move chats : Continue a chat in another folder or a new Git worktree without losing conversation history. Markdown editor : Work on Markdown files more efficiently with features like pasting images, renaming file links, or breadcrumb navigation. Enterprise management : Enforce agent sandboxing and permission policies while controlling which permission modes developers can use.
Redesigned model picker : Quickly switch between Copilot and BYOK contributed models, and manage effort levels and context windows more intuitively. Agents Copilot harness The Copilot harness is powered by the Copilot SDK, a shared foundation that helps align behavior, capabilities, and improvements across Copilot products. In VS Code, the Copilot harness runs sessions through the Agent Host , which lets sessions continue in the background and be accessed from both the VS Code editor window and the Agents window.
The Copilot harness has been available from the harness picker in the chat input. Based on overwhelmingly positive and valuable feedback, we're progressively rolling it out as the default harness for new sessions in VS Code. When you start a new session, Copilot in the harness picker indicates that the session will use the Copilot harness. Thank you to everyone who has shared feedback. We're actively using it to shape the experience.
One example is reintroducing Ask as a built-in agent in the Copilot harness. Your feedback showed that a dedicated read-only experience remains valuable. Select Ask from the agent picker to use it. 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 . Canvases (Preview) Setting : chat.canvases.enabled Open in VS Code Open in VS Code Insiders Canvases are interactive interfaces to collaborate with an agent.
A canvas opens beside the chat, where you and the agent can inspect and update the same artifact instead of coordinating solely through prompts. For example, use a Kanban canvas to plan and track implementation work. You can create and move cards directly, while the agent can break a feature into tasks, update their status, or add newly discovered work. Canvases work in both the VS Code editor window and the Agents window, and canvas extensions are also supported in the GitHub Copilot app .
Canvases are available in Preview in the VS Code desktop app for local sessions that use the Copilot harness. Enable chat.canvases.enabled Open in VS Code Open in VS Code Insiders , and then start a new session with the Copilot harness. Every canvas is provided by a canvas extension. To get started, you have two options: Create a canvas extension : Enter /create-canvas in the chat input and describe the user interface you want for your project.
The skill then creates a canvas extension in your workspace and opens its canvas. Install a chat plugin : For now, install a chat plugin that includes a canvas extension through the GitHub Copilot app. Then switch to VS Code and ask the agent to list the available canvases and have it open one. After you install a canvas extension, you can also open an available canvas in the Agents window from Add Tab (+) > Canvas . Explore and install sample canvas extensions from the community .
Learn more about canvas support in the VS Code documentation. Move chats between folders and worktrees Previously, if you started investigating a task in one folder and then wanted to implement it in a Git worktree, or continue in a different repository, you had to start a new chat and rebuild the context. In the Agents window , you can now ask the agent to move the current chat to another folder or into a new Git worktree, and it keeps the conversation history intact.
Changing the workspace also works for chats that already have a workspace, and the agent can isolate work in a new worktree. Ask the agent with a natural-language prompt, for example: Continue this task in a new Git worktree of the current repository before implementing it. The agent finishes the current turn, moves the chat, and shows a notice when the workspace changes. Then it continues the task automatically in the new location.
Edits and commands run in the new location while your original checkout stays unchanged. The move is available for agent sessions that use the Codex harness or Codex in Interactive mode, and that contain one chat and one local folder. For prerequisites and details about which files are available in the new location, see Move a chat to another folder or worktree . Session-scoped layout in the Agents window (Experimental) Setting : sessions.experimental.layoutScope Open in VS Code Open in VS Code Insiders (Agents window only) Previously, when you switched between sessions in the Agents window, VS Code shared layout settings such as editor visibility, details, and panel visibility across sessions.
If you're used to VS Code remembering the layout for each workspace, sharing the layout across sessions can be disruptive. With the new experimental sessions.experimental.layoutScope Open in VS Code Open in VS Code Insiders setting, you can choose how much of the layout each session remembers. Reload the window after you change the setting. It supports the following values: session-shared (default): The current behavior.
A session and its nested sessions share the same editors and selected panel views. Editor, details, and bottom panel visibility are shared across existing workspace sessions. chat-shared : A session and each of its nested sessions keep their own editors and selected panel views, while editor, details, and bottom panel visibility stay shared across existing workspace sessions. chat : A session and each of its nested sessions also keep their own editor and details composition and bottom panel visibility.
Window geometry, pane sizes, and the sidebar currently remain shared across the window. Customize the Agents window panel layout You can now choose how the bottom panel is aligned in the Agents window. Right-click a panel tab, select Align Panel , and choose one of the following layouts: Center aligns the panel beneath the chat area, leaving more room for the side pane. Justify extends the panel across the full width of the window.
Your selection is saved per profile and preserved when maximizing or restoring the panel. Chat Quickly identify the active harness Chat titles show the active harness name, such as Copilot or Codex , so you can identify it without opening the harness picker or hovering over the session list. Stop background shells In Copilot harness sessions, the background shells pill above the chat input lists the commands that the agent is still running in the background.
When one of those commands is no longer useful, for example a test run that you want to restart or a command that runs longer than expected, you can stop it instead of waiting for it to finish. Select the Background Shells pill, select a shell to open its details, and then select Stop Shell next to its command. Only that command ends, and the shell leaves the list. You can reach Stop Shell with the keyboard, and screen readers announce when the shell stops.
Stopping a shell is only available for attached shells , which the agent runs as part of it
The rest of this page is on the live site.