VS Code 1.146 Gives Your AI Coding Agents an Inbox and a Deadline for the Old Runtime
VS Code 1.146 adds an agent Inbox, Copilot Fusion model comparisons and detachable chat windows, and it starts the countdown to removing the Local harness in February 2027.

An inbox for your AI agents
VS Code 1.146 shipped as a stable release on November 11, and its headline feature is aimed at a problem every developer with an AI coding agent now knows: you are juggling several sessions at once, and you cannot tell which one needs you. The update adds an experimental Inbox mode that collects every session that needs a decision into one list, across all your projects. It is controlled by the setting sessions.list.inboxEnabled, and it is off by default, as most of the new agent features are.
Inbox mode does exactly what the name implies. It gives you one consolidated view of what needs attention, what is running, and what is ready to merge, with in-progress sessions at the top. You can snooze sessions for later instead of losing track of them. If you have ever had three agents working in three workspaces and realized you forgot about one of them for an hour, this is the feature that fixes that.
The release also adds chat windows, in preview, controlled by sessions.chatWindows.enabled. You can pull a session into its own operating system window and rearrange the chat, editors, and terminals around the task. For developers who work with multiple monitors, or who simply want an agent conversation out of the way while they read code, this is a bigger change than it sounds.
Model comparison gets Copilot Fusion
Microsoft also expanded the Compare Models feature in the Agents window. It lets you submit the same prompt to several models, judge the results, and combine them with a synthesizer. Version 1.146 adds chat-only responses that need no workspace selection, Copilot Fusion comparisons, and, experimentally, an agent that can discover models, launch comparisons, and read the results back.
Copilot Fusion is the multi-model routing and orchestration option in GitHub Copilot's model picker, which reached general availability in October. Including it in comparisons means you can test a routed, multi-model answer against single-model answers, which is the comparison that actually matters when you are choosing what to run in production.
Extensions can now be found, installed, and removed without leaving the Agents window, which is an experimental addition that sounds minor and is not. The friction of leaving your agent workflow to manage extensions is exactly the kind of paper cut that makes people stop using a feature. Removing it is good product sense.
The Local harness is going away
The fifth headline item is not a new feature at all: it is a deprecation notice. The Local harness, the original way VS Code ran agent sessions on your own machine, is deprecated and will be removed in February 2027. The Copilot harness, built on the Copilot SDK and running sessions through the Agent Host, has been the default for new sessions since VS Code 1.143 in October.
The reason is security. The Copilot harness enforces managed sandbox policies that the old runtime cannot. As agents gain real muscle, the runtime that runs them needs to be able to limit what they can touch. The Local harness stays usable until February, but it will receive no new functionality. If you pinned it as the default through an enterprise setting, that setting goes away with it.
The security theme runs through the rest of the release too. Permission prompts are now more granular, scoping allowances to specific domains, commands, and directories, instead of the old all-or-nothing prompts. A new setting, chat.agent.sandbox.credentials.envVars, lets you mask environment variables inside sandboxed sessions, with real values reserved for approved HTTPS destinations. And the update adds support for skills delivered through MCP servers, which connects it to the same background MCP tasks that Claude Code gained last week.
VS Code 1.146: what to do this week
If you use VS Code with agents, the update is worth installing now, but the settings are worth reading first. Inbox mode, chat windows, and Copilot Fusion comparisons are all off by default, so nothing changes until you turn them on. Turn on Inbox mode first if you run more than one agent session at a time. It is the feature that pays for itself immediately.
If you are still on the Local harness, start planning the move. Three months is enough time, but the migration is the kind of thing that gets postponed until the week it becomes urgent. Check whether your workflows depend on Local harness behavior, and test them against the Copilot harness now, while both still work.
VS Code is on a weekly release cadence now, and 1.146 is a consolidation step rather than a single marquee feature. That is fine. The editor that most developers live in is being rebuilt, piece by piece, around agents, and this release is the one that admits the truth: the session is now the thing you manage, not the file. The Inbox is the first tool built for that reality, and it will not be the last. For the wider tooling picture, the .NET 11 release and the new Chrome DevTools MCP agent tools landed in the same window, and together they show how fast the agent toolchain is moving.


