{"slug": "visual-studio-code-1-146", "title": "Visual Studio Code 1.146", "summary": "Microsoft released Visual Studio Code 1.146, which deprecates the Local agent harness and schedules its removal for February 2027, while making the Copilot harness — built on the Copilot SDK and running through the Agent Host — the supported path for agent sessions. The release also adds experimental Inbox mode for sessions (via the off-by-default sessions.list.inboxEnabled setting), preview features for model comparison with Copilot Fusion and for chat windows, and experimental extension installation in the Agents window. Microsoft said the Copilot harness enforces managed sandbox and permission policies that the Local harness does not, and that the vscode.temporaryDefaultToLocalHarness enterprise setting introduced in VS Code 1.142 will be removed along with the Local harness.", "body_md": "# Visual Studio Code 1.146\n\n## ## Downloads for 1.146.0\n\n## Release highlights\n\nSave your brainpower for the work that needs it. Inbox mode keeps the right sessions on your radar while agents take on model comparisons. Shape your agent workspace around the task with chat windows and extensions.\n\n- \n[Inbox mode (Experimental)](#_inbox-mode-for-sessions-experimental) : Focus on sessions that need your attention across all your projects, and snooze others for later.\n- \n[Model comparison (Preview)](#_model-comparison-improvements-preview) : Compare results with Copilot Fusion in the mix, or let an agent run comparisons for you.\n- \n[Chat windows (Preview)](#_chat-windows-preview) : Give chats their own windows and rearrange chats, editors, and terminals to fit the task.\n- \n[Extensions in the Agents window (Experimental)](#_install-and-manage-extensions-in-the-agents-window-experimental) : Find and install extensions for a richer agent experience.\n- \n[Local harness deprecation](#_copilot-harness-and-deprecation-of-the-local-harness) : Move to the Copilot harness before the Local harness is removed in February 2027.\n\nHappy coding!\n\nAlready installed? Use **Check for Updates** in VS Code. For upcoming features, use the [Insiders build](https://code.visualstudio.com/insiders).\n\n## Agents\n\n### Copilot harness and deprecation of the Local harness\n\nThe Copilot harness is our latest agent harness and has been the default for new sessions since [VS Code 1.143](https://code.visualstudio.com/updates/v1_143#_copilot-harness-as-the-default). It's built on the Copilot SDK, a shared foundation that helps align behavior, capabilities, and improvements across Copilot products. Copilot harness sessions run through the [Agent Host](https://code.visualstudio.com/docs/agents/concepts/agent-host), so you can keep them running in the background and access them from both the VS Code editor window and the Agents window. For organizations, the Copilot harness also enforces managed sandbox and permission policies that the Local harness doesn't.\n\nThank you to everyone who has shared feedback on using the Copilot harness as your default. Your feedback has shaped the harness experience, and it will continue to guide us through this next step. As of this release, the **Local harness is deprecated and will be removed in three months (February 2027)**:\n\n- **Next three months** : You can still use the Local harness while you move your workflows, but it's functionally frozen. New features and improvements will focus on the Copilot harness and are not guaranteed to be supported by the Local harness.\n- **After three months** : The Local harness will no longer be available. The`vscode.temporaryDefaultToLocalHarness` enterprise-managed setting, introduced in VS Code 1.142 to[keep the Local harness as the default](https://code.visualstudio.com/docs/enterprise/manage-ai-settings#_keep-local-harness-as-default) , will also be removed.\n\nBecause the Copilot harness is already the default for new sessions, you might not need to take any new actions. To confirm you're using the Copilot harness, look for **Copilot** in the harness picker when you start a new session:\n\nIf you still use the Local harness, plan to move completely to the Copilot harness before February 2027. The [Local-to-Copilot harness transition guide](https://code.visualstudio.com/docs/agents/run/move-to-copilot) covers customization compatibility, continuing existing Local conversations, and organization rollout and verification. If you run into any problems, let us know by [filing an issue](https://github.com/microsoft/vscode/issues).\n\n### Inbox mode for sessions (Experimental)\n\n**Setting**: \n      sessions.list.inboxEnabled\n      \n    \n\nKeep track of your agents without checking each workspace. Inbox mode gives you one view of what needs your attention, what's still running, and what's ready to merge.\n\nEnable the \n      sessions.list.inboxEnabled\n      \n    \n setting (off by default), and then select **Grouping > Inbox Mode** in the Agents window's sessions list.\n\nSessions that need your attention appear at the top, above the **Working**, **Ready to merge**, **On hold**, and **Done** groups. If a session can wait, use **Dismiss from Inbox**, **Put on Hold**, or **Snooze** to set it aside. Select **Undo** if you change your mind.\n\nDismissing a session doesn't archive it. To archive it, select **Mark Session as Done**.\n\n### Session list inline actions (Experimental)\n\n**Setting**: \n      sessions.list.inlineActions\n      \n    \n\nFix failing checks and address review comments directly from the Agents window's sessions list. Enable this setting (off by default) to show inline actions for fixing checks, addressing comments, or both.\n\nEach action sends a request to that row's session or nested session in the background without opening it. The setting does not enable Agent Merge or change action permissions.\n\n### Chat windows (Preview)\n\n**Setting**: \n      sessions.chatWindows.enabled\n      \n    \n\nWhen several chats run at once, keeping them all in one Agents window means switching between them and losing sight of the one you are waiting on. With chat windows, you can open a chat in a window of its own, and arrange that window so that the chat, its editors, and its terminals fit the task.\n\nTo try this preview feature in Stable, enable sessions.chatWindows.enabled . It is enabled by default in VS Code Insiders, and off by default in Stable.\n\nLearn more about [chat windows](https://code.visualstudio.com/docs/agents/run/agents-window#_open-chats-in-separate-windows) in our documentation.\n\nTo open a chat in a new window, right-click the session or chat in the sessions list and select **Open in** > **New Window**. You can also drag a chat out of the Agents window to create a new window. You can move it back with the **Move to Main Window** command.\n\nThe following video shows opening a chat in its own window.\n\nA chat window can hold several chats from one or more sessions: pick another session in its title bar, drag a chat in from another window, or select **New Session** (⌘N (Windows, Linux Ctrl+N)) at the left of the title bar to start a new session in that window. Chat windows reopen with their chats and editors after you restart VS Code.\n\nThe content within a chat window is organized into parts, which you can arrange freely to fit your workflow.\n\n- **Move parts:** Drag a part by the grabber on the top edge of its card to another side of the window, or beside another part. You can also use**Move Part Left** ,**Move Part Right** ,**Move Part Up** , and**Move Part Down** .\n- **Move tabs between parts:** Drag a tab to another part, or drop it on a part's edge to split that part. Use**Move Editor to Part** or**Move Editor into New Part Left/Right/Above/Below** to do the same from the Command Palette. Drag an editor tab onto the chat input to attach it to the chat as context.\n- **Place the terminal:** Dragging the terminal under the editor or under the chat sets**Terminal Position** to**Under Editor** or**Under Chat** . Dropping it on the bottom edge of the window sets**Full Width** . You can also change the position from the**...** menu of the terminal.\n- **Switch the layout:** Use**Configure Layout** in the title bar to show the chat, the editor, or both, side by side or stacked. In the stacked layout,**Agents: Toggle Chat Conversation** collapses the chat to only its input, so the editor takes the rest of the window.\n\nUse **Developer: Reset Chat Window Layout** to return a window to how it first opened.\n\nThe following video shows rearranging a chat window and resetting its layout.\n\nLet us know what you think by [filing an issue](https://github.com/microsoft/vscode/issues).\n\n### Install and manage extensions in the Agents window (Experimental)\n\nThe **Extensions** section of Agent Customizations lets you choose which installed extensions run in the Agents window without changing their enablement in editor windows. Previously, adding an extension meant switching to an editor window to install it. In this release, you can find, install, and uninstall extensions without leaving the Agents window:\n\n- **Install from the Marketplace** : Searching also queries the Marketplace and lists matching extensions that you don't have yet, with their publisher, install count, and rating. Installing an extension adds it to VS Code and enables it in the Agents window. To install a different version, such as a pre-release, use the dropdown next to**Install** .\n- **Know what won't work before installing** : Extensions that contribute views, debuggers, status bar items, or walkthroughs without declaring support for the Agents window show a warning that lists the unsupported features. Extensions that can't be installed, for example because your organization doesn't allow them, show the reason.\n- **Open with a keyboard shortcut** : Press ⇧⌘X (Windows, Linux Ctrl+Shift+X) or run**Extensions: Manage Extensions** to open the section. If you changed the shortcut for the Extensions view in editor windows, your shortcut also works in the Agents window.\n\n### Model comparison improvements (Preview)\n\n**Setting**: \n      sessions.chat.compareAgents.tools.enabled\n      \n    \n\n[Compare Models](https://code.visualstudio.com/docs/agents/run/compare-models) in the Agents window lets you run the same prompt across models, evaluate their results with a judge, and combine their strengths with a synthesizer. This release makes comparisons easier to configure, organize, and automate:\n\n- **Judge and synthesize chat-only responses** : Add a judge and synthesizer without selecting a workspace. Synthesis starts when you select**Synthesize** and creates a new chat without changing the original attempts.\n- **Compare Copilot Fusion** : Select Fusion and its supported effort tiers for an attempt, the judge, or the synthesizer.\n- **Let an agent run evaluations (Experimental)** : Enable \n      sessions.chat.compareAgents.tools.enabled\n      \n    \n to let agents discover models, launch comparisons, and read results and conversation references to summarize findings across scenarios. The tools are off by default and require Compare Models to be enabled. Disabling them still leaves manual comparisons available.\n\n### Canvases improvements (Preview)\n\n**Setting**: \n      chat.canvases.enabled\n      \n\n[Canvases](https://code.visualstudio.com/docs/agents/run/canvases) are shared, interactive surfaces where you and Copilot work together on plans, dashboards, and other artifacts. This release adds permission prompts and improves canvas discovery and continuity:\n\n- **Permissions for canvas extensions** : In Copilot harness sessions, canvas extensions ask for your approval before initializing privileged capabilities, such as hooks.\n- **Find and reopen canvases** : Canvas menus distinguish**Running** canvases from**Available** canvases you can create new instances for. In the Agents window, actions to create or install canvases appear under**Discover More** .\n- **Resume without another prompt** : When you return to an inactive Copilot harness session, its canvases restore without sending another message.\n- **Smoother reconnection** : While a canvas provider restarts, the last canvas image stays visible with a reconnecting indicator.\n- **Keep canvases with their chats** : In separate chat windows, canvas tabs close when their chat leaves the window and can reopen alongside it. Canvases also restore after a window reload without taking focus.\n\n### Configure computer sharing (Experimental)\n\n**Setting**: \n      sessions.chat.experimental.remoteEnvironmentsThisComputer\n      \n    \n\nThe Remote Environments editor in the Agents window is a central place for managing remote connections. In this release, you can now manage how this computer is shared with other clients. Regardless of whether sharing is enabled, local sessions continue to run directly on this computer.\n\nShare this computer through GitHub Environments or Dev Tunnels, or turn sharing off. You can also change the computer name that other clients see.\n\nOpen the editor with **Manage Remote Environments** from the Environment picker in chat, the Command Palette, or the title bar's **Remote Connections** menu (antenna icon), which also offers the same sharing options.\n\nLearn more about [making a host available for remote access](https://code.visualstudio.com/docs/agents/run/remote-agent-sessions#_make-a-host-available-for-remote-access).\n\n### Agent Host support for virtual repositories\n\nVS Code supports virtual workspaces, allowing you to do things like [viewing a GitHub repository without having to clone it](https://code.visualstudio.com/docs/sourcecontrol/github#_github-repositories-extension).\n\nThe Copilot harness previously did not work in virtual repositories. In this release, we added support for virtual repositories, so you can use the same Copilot features and workflows as you do in local folders.\n\n## Chat\n\n### Continue a Copilot CLI session in VS Code (Experimental)\n\nWhen you're working with the [GitHub Copilot CLI](https://github.com/features/copilot/cli) in a terminal outside VS Code, you can now move the session into VS Code and keep going.\n\nEnter `/code` in the CLI, or `/code-insiders` for VS Code Insiders. The CLI exits, and VS Code opens the same session in the Chat view of the window for the session's folder, starting VS Code if it isn't running. The session keeps its conversation history, its model and reasoning effort, and its mode and permissions.\n\nThe `/code` command is experimental in Copilot CLI. It requires Copilot CLI 1.0.107 or later, with experimental features turned on (`/settings experimental on`). Permissions that apply only to the CLI process, such as `--allow-tool` or approvals you granted for the session, don't carry over, and the CLI lists them before handing off. If another Copilot CLI process still has the session open, VS Code asks before opening it. To return to the CLI, run the `copilot --resume` command that the CLI shows when it hands off.\n\n### Configurable shortcut for the background send action\n\n**Setting**: \n      chat.sendInBackgroundTip.enabled\n      \n    \n\nStart a new session without opening it by pressing ⌘Enter (Windows, Linux Ctrl+Enter) in the Agents window composer. You can rebind or remove the shortcut for **Chat: Send in Background** in **Keyboard Shortcuts**.\n\nAn optional tip shows your configured shortcut and links to **Keyboard Shortcuts**. Enable it with \n      chat.sendInBackgroundTip.enabled\n      \n    \n (Experimental, off by default).\n\n## MCP\n\n### Skills over MCP (Preview)\n\n**Setting**: \n      chat.agentHost.mcpSkills.enabled\n      \n    \n\nThis release of VS Code adds support for SEP-2640 [Skills over MCP](https://github.com/modelcontextprotocol/ext-skills), allowing MCP servers to automatically provide skills to the model.\n\nThe first time you connect to an MCP server that provides skills, you are asked to allow them into your model context. Afterwards, the model can interact with these skills and you can see them on the **Skills** tab of the Agent Customizations editor.\n\n## Trust and security\n\n### Improved permission prompts\n\nThe Copilot harness previously suggested overly broad tool-level allowances for operations like web fetches, terminal commands, and file reads. For example, the default action for fetching a URL was \"Allow in this Session\", which would let the model access any URL during that session.\n\nNow, permission prompts are more granular, by default adding allowances for specific domains, commands, and directories.\n\n### Mask environment variables in the sandbox\n\n**Setting**: \n      chat.agent.sandbox.credentials.envVars\n      \n    \n\nTo protect sensitive information, you can configure which environment variables are masked in sandboxed sessions and hidden from agent tools. Sandboxed tools receive placeholders, and the real values are supplied only to approved HTTPS destinations.\n\nIn this example, sandboxing replaces the value of the `API_TOKEN` environment variable with a placeholder. The real value is restored only in outgoing HTTPS requests to hosts listed in `injectHosts`, here `api.example.com`. Requests to other hosts retain the placeholder and don't receive the actual value.\n\n```\n{\n  \"chat.agent.sandbox.credentials.envVars\": {\n    \"API_TOKEN\": {\n      \"injectHosts\": [\"api.example.com\"]\n    }\n  }\n}\n```\n\nEnter variable names, not secret values, in settings. On Windows, environment variable masking requires local-network access. On macOS and Windows, trust the sandbox CA certificate for tools that require OS certificate trust.\n\nSee [sandbox network access](https://code.visualstudio.com/docs/agents/run/agent-sandboxing#_configure-network-access) and [certificate trust](https://code.visualstudio.com/docs/agents/run/agent-sandboxing#_trust-the-sandbox-ca-certificate-on-windows-and-macos) for more information.\n\n### Sandbox status in the chat input\n\nSee whether terminal sandboxing is enabled without opening the Permissions menu. In both the editor and the Agents window, the empty chat input shows **(sandbox enabled)** when **Sandboxing for terminal** is on. The placeholder stays in sync as you switch chats or change the setting.\n\n## Accessibility\n\n### Visible keyboard focus on Welcome\n\nThe Welcome page shows a visible outline when the page itself has keyboard focus, so you can track your position while navigating. The page remains focusable for screen reader users.\n\n## Editor Experience\n\n### Mermaid 12 support\n\nVS Code now uses Mermaid 12 when rendering Mermaid diagrams in chat, Markdown previews, and notebooks. You can use new diagram types, including use-case diagrams, and benefit from updated automatic layout behavior.\n\n| Before: Mermaid 11 | After: Mermaid 12 | \n|---|---|\n\n### Copy the address of local HTML files in the Integrated Browser\n\nWhen you preview a local HTML file in the [Integrated Browser](https://code.visualstudio.com/docs/debugtest/integrated-browser), you can select and copy its `file://` address to paste it into an external browser or a terminal.\n\n## Enterprise\n\n### Copilot sessions behind enterprise proxies\n\nCopilot sessions follow VS Code's [proxy configuration](https://code.visualstudio.com/docs/setup/network), including proxy auto-configuration (PAC) and Kerberos authentication, when running locally, in WSL, or in a local Dev Container. Your organization's routing rules can select different proxies or a direct connection for each destination, rather than forcing requests through a single proxy.\n\n### Organization help links for policy restrictions\n\nOrganizations can direct blocked developers to their own help page by setting `communication.support.url` in [enterprise-managed settings](https://code.visualstudio.com/docs/enterprise/manage-ai-settings). We recommend pointing this URL to a page where employees can find their organization's Copilot usage policies and support guidance. A valid absolute HTTP or HTTPS URL adds **Contact Admin** links to supported policy restrictions, such as disabled Agents or organization-disabled models.\n\nFor example, in your organization's managed settings:\n\n```\n{\n  \"communication\": {\n    \"support\": {\n      \"url\": \"https://ai.example.com/your-companys-ai-landing-support-page\"\n    }\n  }\n}\n```\n\n### Enterprise controls for canvas extensions\n\nIn Copilot harness sessions, `strictPluginOnlyCustomization` already restricted standalone skills, agents, hooks, and MCP servers. It now also blocks standalone canvas extensions from user, project, and session directories, so administrators can require that any canvas extensions used come from eligible plugins.\n\nIn [enterprise-managed settings](https://docs.github.com/en/copilot/how-tos/administer-copilot/manage-for-enterprise/use-managed-settings/get-started), use `true` to block all supported standalone categories while allowing eligible plugin content:\n\n```\n{\n  \"strictPluginOnlyCustomization\": true\n}\n```\n\nTo restrict only selected categories, replace `true` with a list containing any of `\"skills\"`, `\"agents\"`, `\"hooks\"`, `\"mcp\"`, and `\"extensions\"`.\n\n**Note:** VS Code's boolean-only `ChatStrictPluginOnlyCustomization` policy does not control canvas extensions. The Copilot SDK manages them, so use the Copilot managed setting above.\n\nSee the [enterprise-managed settings reference](https://docs.github.com/en/copilot/reference/enterprise-administrators/enterprise-managed-settings) for policy details.\n\n## Deprecated features and settings\n\n### New deprecations in this release\n\n- [The Local harness is deprecated](#_copilot-harness-and-deprecation-of-the-local-harness) and will be removed in February 2027.\n\n### Upcoming deprecations\n\nNone\n\n## Notable fixes\n\n### Fixed overcounting in agent edit metrics\n\nAgent edit metrics reported through [GitHub Copilot usage metrics](https://docs.github.com/en/copilot/reference/copilot-usage-metrics) no longer count unchanged text between edits as newly added or deleted code.\n\n## Thank you\n\n### Issue tracking\n\nContributions to our issue tracking:\n\n- [@gjsjohnmurray (John Murray)](https://github.com/gjsjohnmurray)\n- [@RedCMD (RedCMD)](https://github.com/RedCMD)\n- [@IllusionMH (Andrii Dieiev)](https://github.com/IllusionMH)\n- [@albertosantini (Alberto Santini)](https://github.com/albertosantini)\n\n### Pull requests\n\nContributions to `vscode`:\n\n- [@Aditya-kumar-yadav (Aditya Kumar Yadav)](https://github.com/Aditya-kumar-yadav) : terminal: fix collapseTildePath substring collisions and exact home collapse[PR #343203](https://github.com/microsoft/vscode/pull/343203)\n- [@alok-108 (Alok Pandey)](https://github.com/alok-108) : debug: send the mode of exception breakpoints to the debug adapter[PR #341972](https://github.com/microsoft/vscode/pull/341972)\n- [@andysalerno (Andy Salerno)](https://github.com/andysalerno) : Show Copilot Fusion reasoning in the agent host chat[PR #346434](https://github.com/microsoft/vscode/pull/346434)\n- [@Carrotstudiosoftwarehouse (Carrotstudio.it)](https://github.com/Carrotstudiosoftwarehouse) : Keep the full URI reachable in the prompt URL confirmation dialog[PR #332937](https://github.com/microsoft/vscode/pull/332937)\n- [@Chethan616 (Chethan Krishna)](https://github.com/Chethan616) : Fix terminal not focusing when clicking blank space below inline chat widget[PR #334804](https://github.com/microsoft/vscode/pull/334804)\n- [@ericbaum (Eric Baum)](https://github.com/ericbaum) : mcp: use URI-backed defaultCwd for home-directory discovery adapters[PR #345650](https://github.com/microsoft/vscode/pull/345650)\n- [@genius-0963 (Saurabh Sungh)](https://github.com/genius-0963) : Fix #345692: Preserve draft open editors when replacing new draft session[PR #345807](https://github.com/microsoft/vscode/pull/345807)\n- [@LuisPeixoto (Luis Peixoto)](https://github.com/LuisPeixoto) : Fix Hooks section description[PR #346593](https://github.com/microsoft/vscode/pull/346593)\n- [@maxteneff (Max Bartenev)](https://github.com/maxteneff) : Fix parentTerminal being ignored for terminals that have already opened[PR #342420](https://github.com/microsoft/vscode/pull/342420)\n- [@mcumming (Michael Cummings (MSFT))](https://github.com/mcumming)  - Fix marketplace 403 responses prompting repeated sign-in [PR #343686](https://github.com/microsoft/vscode/pull/343686)\n  - Private Marketplace extension blocking: add workbench UX and update gating [PR #341049](https://github.com/microsoft/vscode/pull/341049)\n  - Do not forward request credentials across origins on redirects [PR #343690](https://github.com/microsoft/vscode/pull/343690)\n  - Cache and coalesce marketplace protected resource discovery [PR #343687](https://github.com/microsoft/vscode/pull/343687)\n- Fix marketplace 403 responses prompting repeated sign-in \n- [@minwookshin (Minwook Shin)](https://github.com/minwookshin) : Honor explicit inline edit gutter menu visibility[PR #339575](https://github.com/microsoft/vscode/pull/339575)\n- [@monil-patel](https://github.com/monil-patel) : Allow Policy Helper registration through VS Code settings[PR #345712](https://github.com/microsoft/vscode/pull/345712)\n- [@nkramber](https://github.com/nkramber)  - Keep terminal editors working after moving them to another editor group [PR #339488](https://github.com/microsoft/vscode/pull/339488)\n  - Find terminal profiles at the login shell path when it's not on PATH [PR #339556](https://github.com/microsoft/vscode/pull/339556)\n- Keep terminal editors working after moving them to another editor group \n- [@RealThanhNguyxn (Thanh Nguyen)](https://github.com/RealThanhNguyxn) : Preserve unresolved variables in process task command path (fixes #160891)[PR #316369](https://github.com/microsoft/vscode/pull/316369)\n- [@rksharma-owg (RKS)](https://github.com/rksharma-owg)  - tasks: pass task type through ITaskHandleDTO to prevent provider fanout [PR #336159](https://github.com/microsoft/vscode/pull/336159)\n  - Flush final task markers before completion notification [PR #339551](https://github.com/microsoft/vscode/pull/339551)\n  - Preserve distinct task errors from the same resource [PR #339550](https://github.com/microsoft/vscode/pull/339550)\n- tasks: pass task type through ITaskHandleDTO to prevent provider fanout \n- [@ShehabSherif0 (Shehab Sherif)](https://github.com/ShehabSherif0) : Fix duplicated condition in accessibility signal property change detection[PR #303604](https://github.com/microsoft/vscode/pull/303604)\n- [@SimonSiefke (Simon Siefke)](https://github.com/SimonSiefke)  - perf: make the Test Explorer faster when running many tests [PR #345896](https://github.com/microsoft/vscode/pull/345896)\n  - fix: memory leak in notebook text diff editor [PR #331805](https://github.com/microsoft/vscode/pull/331805)\n  - fix: memory leak in color picker [PR #345461](https://github.com/microsoft/vscode/pull/345461)\n  - fix: memory leak in aiSearchModel [PR #342528](https://github.com/microsoft/vscode/pull/342528)\n  - fix: memory leak in file search listeners [PR #345781](https://github.com/microsoft/vscode/pull/345781)\n  - fix: memory leak in terminal find widget [PR #346139](https://github.com/microsoft/vscode/pull/346139)\n  - fix: memory leak in search progress emitter [PR #346126](https://github.com/microsoft/vscode/pull/346126)\n  - perf: reduce memory usage by 24 kB [PR #342397](https://github.com/microsoft/vscode/pull/342397)\n  - fix: task provider counter bug [PR #339387](https://github.com/microsoft/vscode/pull/339387)\n  - fix: memory leak in marker resource maps [PR #346501](https://github.com/microsoft/vscode/pull/346501)\n  - fix: memory leak in debouncedObservable [PR #346498](https://github.com/microsoft/vscode/pull/346498)\n  - fix: memory leak in keybindings search [PR #346268](https://github.com/microsoft/vscode/pull/346268)\n- perf: make the Test Explorer faster when running many tests \n- [@sumit-2007-git (Sumit kumar)](https://github.com/sumit-2007-git) : fix(chat): truncate suggested prompt titles to prevent overflow in narrow chat (fixes #275257)[PR #345436](https://github.com/microsoft/vscode/pull/345436)\n- [@vscodebot-pr (VS Code PR Bot)](https://github.com/vscodebot-pr)  - fix: guard terminal scroll operations before renderer is attached (fixes #339313) [PR #339330](https://github.com/microsoft/vscode/pull/339330)\n  - fix: guard notebook cursor-selection reveal during cell disposal (fixes #328986) [PR #329000](https://github.com/microsoft/vscode/pull/329000)\n- fix: guard terminal scroll operations before renderer is attached (fixes #339313) \n- [@xingsy97 (xingsy97)](https://github.com/xingsy97) : terminal: fix type-ahead prediction incorrectly rejecting valid style sequences[PR #305103](https://github.com/microsoft/vscode/pull/305103)\n- [@zohnannor](https://github.com/zohnannor) : fix: remove regression causing minimap to always have opacity[PR #311689](https://github.com/microsoft/vscode/pull/311689)\n\nWe really appreciate people trying our new features as soon as they are ready, so check back here often and learn what's new.\n\nIf you'd like to read release notes for previous VS Code versions, go to [Updates](https://code.visualstudio.com/updates) on [code.visualstudio.com](https://code.visualstudio.com).", "url": "https://wpnews.pro/news/visual-studio-code-1-146", "canonical_source": "https://code.visualstudio.com/updates/v1_146", "published_at": "2026-11-11 17:00:00+00:00", "updated_at": "2026-11-18 09:42:16.975570+00:00", "lang": "en", "topics": ["ai-agents", "developer-tools", "ai-products"], "entities": ["Microsoft", "Visual Studio Code", "GitHub Copilot", "Copilot SDK", "Agent Host", "Copilot Fusion"], "also_reported_by": [], "takeaway": "Move agent workflows from the deprecated Local harness to the Copilot harness before February 2027, since the Local harness is functionally frozen and the vscode.temporaryDefaultToLocalHarness enterprise setting will be removed with it.", "recommendation": null, "alternates": {"html": "https://wpnews.pro/news/visual-studio-code-1-146", "markdown": "https://wpnews.pro/news/visual-studio-code-1-146.md", "text": "https://wpnews.pro/news/visual-studio-code-1-146.txt", "jsonld": "https://wpnews.pro/news/visual-studio-code-1-146.jsonld"}}