GitHub Copilot in VS Code v1.142
GitHub Copilot in VS Code v1.142 was released on .
Summary
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 Copi...
Release Context
- This was the 12th GitHub Copilot in VS Code release of 2026 tracked by Havoptic.
- It shipped 7 days after GitHub Copilot in VS Code v1.141 (October 7, 2026).
Shipped around the same time
Within 3 days of this release, other AI coding tools also shipped:
- Claude Code v2.1.302 (October 16, 2026)
- OpenCode v1.19.3 (October 16, 2026)
- Cline v4.1.25 (October 16, 2026)
- Antigravity CLI v1.4.0 (October 16, 2026)
- OpenCode v1.19.2 (October 16, 2026)
Compare GitHub Copilot in VS Code
- GitHub Copilot in VS Code vs Claude Code
- GitHub Copilot in VS Code vs OpenAI Codex CLI
- GitHub Copilot in VS Code vs Cursor
- GitHub Copilot in VS Code vs Gemini CLI
- GitHub Copilot in VS Code vs Kiro CLI
- GitHub Copilot in VS Code vs GitHub Copilot CLI
- GitHub Copilot in VS Code vs Devin Desktop
- GitHub Copilot in VS Code vs Antigravity CLI
- GitHub Copilot in VS Code vs Grok Build
- GitHub Copilot in VS Code vs Cline
- GitHub Copilot in VS Code vs OpenCode
- GitHub Copilot in VS Code vs Zed
- GitHub Copilot in VS Code vs Factory Droid
- GitHub Copilot in VS Code vs Devin
- GitHub Copilot in VS Code vs Lovable
- GitHub Copilot in VS Code vs Amp
- GitHub Copilot in VS Code vs Replit Agent
- GitHub Copilot in VS Code vs Bolt
- GitHub Copilot in VS Code vs v0
Release Notes
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 rollin... Canvases (Preview) Setting: setting(chat.canvases.enabled) 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 s... 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 wo... Session-scoped layout in the Agents window (Experimental) Setting: setting(sessions.experimental.layoutScope) (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 setting(sessions.experimental.layoutScope) setting, you can choose how much of the layout each session remembers. Reload the win... 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.... Stateful responses for BYOK custom endpoints If your bring-your-own-key (BYOK) model uses a stateless Responses API, set "statefulResponses": false on its model entry in chatLanguageModels.json to send full conversation history with each request. See Custom Endpoint configuration for details. Windows sandboxing for Local harness is no longer supported Windows sandboxing for terminal commands in Local agent sessions has been deprecated. For sandboxed command execution on Windows, use an Agent Host session. See the Agent Host sandboxing documentation for details. Redesigned model picker Copilot and bring-your-own-key (BYOK) providers offer many models, each with strengths for different tasks. The redesigned model picker makes it easier to choose and switch models as your work changes. The model picker uses a tabbed interface to separate Copilot and BYOK models. When you hover over a model in the list, you can further configure its thinking level and context window size. Enterprise Automatically move policy-managed chats to Copilot Agent Host Enterprise managed settings let administrators govern agent permissions and sandboxing. When your organization configures a nonempty permissions object or sets sandbox.enabled to true, VS Code now requires the Copilot harness in Agent Host for full chat sessions, to be able to enforce these policies. Opening an existing, unarchived Local chat automatically moves it to Copilot, preserving the transcript and unsent draft, including attachments. Not... Temporarily keep the Local harness Administrators who need more time to transition to Copilot Agent Host can set vscode.temporaryDefaultToLocalHarness to true in their unified managed settings: json { "vscode": { "temporaryDefaultToLocalHarness": true } } This keeps the Local harness available and stops automatic switching to Copilot, while preserving explicit, remembered, and current harness choices. Set the managed value to fals... Manage Copilot permission modes independently Administrators can permit Assisted while blocking Allow All, giving developers assisted approvals without bypassing permission checks. The Copilot permission picker reflects the modes permitted by your organization's managed settings. For example, merge this configuration into your unified managed settings: json { "permissions": { "disableBypassPermissionsMode": "disable", "disableAssistedP...
Other Recent GitHub Copilot in VS Code Releases
- v1.140 (September 30, 2026)
- v1.139 (September 23, 2026)
- v1.138 (September 16, 2026)
- v1.137 (September 9, 2026)
- v1.136 (September 2, 2026)
All GitHub Copilot in VS Code releases · All AI coding tool releases on Havoptic