GitHub Copilot in VS Code v1.145

GitHub Copilot in VS Code v1.145 was released on .

Summary

VS Code 1.145 is here: preview remote apps from the Agents window, mix agent harnesses in one session, and schedule automations with cron. Your MCP allowlist just got smarter too. Curious what else shipped?

Release Context

  • This was the 15th GitHub Copilot in VS Code release of 2026 tracked by Havoptic.
  • It shipped 7 days after GitHub Copilot in VS Code v1.144 (October 28, 2026).
  • GitHub Copilot in VS Code: ships every 7 days — 4 releases in the last month.

Why it matters: Browse and preview remote agent apps in VS Code.

Shipped around the same time

Within 3 days of this release, other AI coding tools also shipped:

Compare GitHub Copilot in VS Code

Release Notes

Remote agents Browse over remote agent host connections (Preview) Setting: setting(workbench.browser.enableRemoteProxy) When an agent session runs on a remote agent host, the integrated browser in the Agents window now loads pages through that host, as it already does in remote workspaces. When the agent starts a dev server on the remote machine, you can open it right in the Agents window to preview the app, validate the agent's changes... Remote canvases (Preview) Settings: setting(workbench.browser.enableRemoteProxy), setting(chat.canvases.enabled) Thanks to the remote agent host connections support, you can now also use canvases that are hosted on a remote agent host. Enable setting(chat.canvases.enabled) and setting(workbench.browser.enableRemoteProxy) to try it out, and file any issues you encounter in the VS Code repository. Agents Mix and match agent harnesses in one session (Preview) Setting: setting(chat.agentHost.multipleChatProviders.enabled) Nested sessions let you keep related conversations together within a single main chat session. Previously, every nested session inherited its parent session's harness. If you wanted a second opinion from another agent, you had to start a separate session and lose that grouping. In this release, nested sessions can use different harnesses than their parent s... Cron schedules and custom agents for local automations Instead of manually running agent tasks one by one, you can use automations to schedule and run them automatically, either on demand or on a set schedule. This release gives you more flexibility for local automations and keeps the Automations view focused on active work: Use cron schedules: Select Cron to enter a five-field cron expression when the other schedule presets aren't precise enough. The dialog validates the expression and describes the resulting sch... Pin canvases to sidebar (Experimental) Setting: setting(chat.canvases.enabled) To make it easier to access frequently used canvases, you can now pin a canvas to appear in the left sidebar. To pin a canvas, open it and select the Add to Sidebar button above the canvas. Pinned canvases remain accessible in the sidebar even when you navigate away from them. Copilot harness The Copilot harness continues to be the default for new sessions in VS Code. It's our latest harness, built on the Copilot SDK, a shared foundation that helps align behavior, capabilities, and improvements across Copilot products. When you start a new session, Copilot in the harness picker indicates that the session uses the Copilot harness. In VS Code, you can keep Copilot harness sessions running in the background and access them from both the VS Code editor window and the Agents window. These sessions run through the Agent Host Setting: setting(chat.editor.workingSet.enabled) Last release, we introduced the working set for Copilot harness sessions, letting you review pending agent edits. You can keep or undo changes, as you could do with the Local harness. We are further improving the working set experience in Copilot harness sessions: Files in WSL, Dev Containers, and SSH workspaces open from the working set on the correct host. When several tool calls edit the same file in parallel, the working set tracks those edits and the editor's inline review... Improved guidance when required sandboxing is unavailable Agent sandboxing limits what terminal commands can access, like the file system and network resources. Your organization can require it with managed settings that disallow bypassing the sandbox. If your organization requires sandboxing but your machine can't run it, the warning banner explains why terminal commands are blocked and how to resolve the problem. It shows the specific cause, such as a missing dependency, and links to troubleshooting steps. If your ac... Chat Choose agent verbosity (Experimental) Setting: setting(chat.persistentProgressVerbosity) Keep long chats readable, or follow the agent's reasoning and tool calls in detail when you need to understand its actions. Open the Chat view's More Actions menu and select View Mode: Conversation: Focus on the conversation. Reasoning and tool calls are grouped into collapsed sections between blocks of response text. Expand a section to inspect its details. Verbose: Follow each step with tool calls expanded, without an internal scrolling limit on tool groups. Compac... Chat performance improvements Reopen and browse long Copilot harness chats more smoothly. VS Code reuses existing reasoning titles and renders terminal output as you reveal it. Terminal output in restored tool calls is rendered when you expand or reveal it, rather than all at once. This release also reduces repeated progress updates and layout measurements when restoring and navigating long conversations. Inline chat attachments (Experimental) Setting: setting(chat.inlineAttachments.enabled) Keep file references and other context next to the instructions they belong to. Enable this setting to insert attachment pills at the cursor in your prompt, rather than in a separate row above the input. Move across, select, or delete an attachment pill as a single character. Previous messages keep the pills inline, so references stay with the surrounding instructions. Inline attachments are on by default in Insiders and off by default in Stable. Attach files from anywhere on your computer Previously, to give chat a file outside your workspace, such as a screenshot or mockup on your desktop, you had to drag it in from your file manager or ask the agent to find it. Select Add Context (+) > Files to choose one or more files with the standard file dialog, even in a new chat without a workspace. In cloud sessions, the chooser lists only images. When sandboxing is enabled in Copilot harness sessions, the agent can read the files and folders you attach, even... MCP Support for tools provided by MCP apps MCP apps are interactive interfaces provided by MCP servers. They can now register tools that the language model can call in its next request. For example, the ShaderToy server lets the model iterate on shaders in real time. Managed MCP allowlist precedence For MCP servers started by VS Code, the enterprise-managed allowedMcpServers list takes precedence over registry-only access, so your organization can approve servers without publishing them to its registry. See the Enterprise section on managed MCP allowlists for configuration details and restrictions. Enterprise Managed MCP allowlists take precedence over registry-only access Previously, when an organization limited MCP to servers from its registry and also defined an allowlist in managed settings, VS Code still required each server to be in the registry. Servers that the allowlist approved but that weren't published to the registry couldn't run. The enterprise-managed allowedMcpServers list is now authoritative. A server that matches the list can run even if it isn't in the registry, and a registry server that doesn't match is blocked. For example, the following [enterprise-managed setting...

View original release

Other Recent GitHub Copilot in VS Code Releases

All GitHub Copilot in VS Code releases · All AI coding tool releases on Havoptic