VS Code 1.146: Power-User Guide to Inbox Mode, Chat Windows and Harness Changes

Last updated: November 17, 2026

VS Code 1.146, released November 11, 2026, adds an Inbox mode for agent sessions, chats in separate windows, agent-run model comparisons and extension installs inside the Agents window. It also deprecates the Local harness, which will be removed in February 2027 in favor of the Copilot harness.

Contents

What changed in VS Code 1.146

Microsoft’s VS Code 1.146 release notes focus on managing several AI agent sessions at once. The main additions are:

  • Inbox mode (Experimental): one view of the sessions that need you, across all your projects.
  • Chat windows (Preview): move a chat into its own window and arrange its editors and terminals around it.
  • Model comparison (Preview): compare Copilot Fusion against other models, or let an agent run comparisons for you.
  • Extensions in the Agents window (Experimental): find, install and remove extensions without switching to an editor window.
  • Local harness deprecation: move to the Copilot harness before February 2027.

The release also adds Skills over MCP, finer-grained permission prompts and masking of environment variables in sandboxed sessions.

New features, status and settings

Most new features sit behind settings. The table lists what the release notes state for each one.

Feature Status Setting Default
Inbox mode for sessions Experimental sessions.list.inboxEnabled Off
Session list inline actions Experimental sessions.list.inlineActions Off
Chat windows Preview sessions.chatWindows.enabled Off in Stable, on in Insiders
Agent-run model comparisons Experimental sessions.chat.compareAgents.tools.enabled Off
Canvases improvements Preview chat.canvases.enabled Not stated
Computer sharing Experimental sessions.chat.experimental.remoteEnvironmentsThisComputer Not stated
Skills over MCP Preview chat.agentHost.mcpSkills.enabled Not stated
Background send shortcut tip Experimental chat.sendInBackgroundTip.enabled Off

Local harness vs Copilot harness

The harness is the software that coordinates the model, context and tools for Copilot agent sessions. The Copilot harness has been the default for new sessions since VS Code 1.143. With 1.146, the Local harness is deprecated and functionally frozen. It will be removed in February 2027, along with the vscode.temporaryDefaultToLocalHarness enterprise setting.

According to GitHub’s November 16 changelog, the Copilot harness is built on the Copilot SDK and shares its coding-agent runtime with Copilot CLI and the GitHub Copilot app. It offers:

  • Copilot Fusion model selection and, on supported tiers, coordinated drafting and review.
  • Assisted permissions, which reduce approval interruptions. Calls the risk assessment does not approve still come to you.
  • Copilot connectors (preview), which bring in context from your team’s services without configuring MCP servers yourself.
  • Sessions that keep running in the background through the Agent Host, available in both the editor and the Agents window.

Choosing the Copilot harness does not move your files to the cloud, and you can keep your existing plan, including Copilot Free. For background on the harness itself, see our Microsoft Copilot Harness guide, and for Fusion effort levels, our GitHub Copilot Fusion guide.

How to set up the new agent workflow

  1. Update VS Code. Use Check for Updates and confirm you are on 1.146.
  2. Confirm the harness. Start a new session and check that Copilot is selected in the harness picker (Session Target).
  3. Turn on Inbox mode. Enable sessions.list.inboxEnabled, then select Grouping > Inbox Mode in the Agents window’s sessions list.
  4. Triage sessions. Sessions that need attention appear above the Working, Ready to merge, On hold and Done groups. Use Dismiss from Inbox, Put on Hold or Snooze to set one aside, and Mark Session as Done to archive it.
  5. Open a chat window. Enable sessions.chatWindows.enabled, right-click a chat and select Open in > New Window. Use Configure Layout to show the chat, the editor or both.
  6. Add extensions. Press Ctrl+Shift+X (Cmd+Shift+X on macOS) in the Agents window to search, install or uninstall extensions.
  7. Automate comparisons. With Compare Models enabled, turn on sessions.chat.compareAgents.tools.enabled so agents can launch comparisons and summarize the results.

Two smaller workflow additions are worth knowing. Inline actions in the sessions list can fix failing checks or address review comments in the background without opening the session. And Ctrl+Enter (Cmd+Enter on macOS) in the Agents window composer starts a session in the background.

If you work in the terminal, Copilot CLI 1.0.107 or later can hand a session to VS Code with the experimental /code command. The session keeps its history, model, reasoning effort, mode and permissions. CLI-only permissions such as --allow-tool do not carry over. Our Copilot CLI 1.0.111 guide covers recent CLI changes.

Security and MCP changes

Several changes affect what agents can reach:

  • Granular permission prompts: the Copilot harness previously suggested broad allowances, such as allowing any URL for a session. Prompts now default to specific domains, commands and directories.
  • Environment variable masking: chat.agent.sandbox.credentials.envVars replaces chosen variables with placeholders in sandboxed sessions. The real value is sent only in HTTPS requests to hosts listed in injectHosts.
  • Sandbox status: the empty chat input shows “(sandbox enabled)” when terminal sandboxing is on.
  • Skills over MCP (Preview): MCP servers can provide skills to the model under SEP-2640. VS Code asks before adding them to the model context the first time.
  • Enterprise controls: strictPluginOnlyCustomization now also blocks standalone canvas extensions, and communication.support.url adds Contact Admin links to policy restrictions.

How 1.146 compares with 1.145

VS Code 1.145, released November 4, 2026, focused on remote agent sessions. It added app previews and canvases for remote agents, cron schedules for automations, an agent verbosity control and folder exclusions. Version 1.146 shifts attention to handling many sessions at once.

Area VS Code 1.145 (Nov 4) VS Code 1.146 (Nov 11)
Session management Remote sessions feel more local Inbox mode, inline actions, chat windows
Automation Cron schedules for recurring agent tasks Agents can run model comparisons
Canvases Canvases in remote agent sessions Permission prompts, restore without a new prompt
Harness Copilot harness default, Local still supported Local harness deprecated, removal in February 2027

For scheduled agent work, see our Copilot Automations guide. Teams on GitHub Enterprise Server can compare this with the GitHub Copilot app guide.

Limitations to know

  • Inbox mode, inline actions, agent-run comparisons and computer sharing are experimental and off by default. Chat windows are a preview feature.
  • Switching harnesses does not automatically convert every customization, so review yours before February 2027.
  • Selecting the Copilot harness does not turn on sandboxing. Administrators configure that separately.
  • Editor-provided tools still require a connected editor.
  • Extensions that contribute views, debuggers, status bar items or walkthroughs without declaring Agents window support show a warning before install.
  • On Windows, environment variable masking requires local-network access.

Frequently asked questions

When was VS Code 1.146 released?

Microsoft released Visual Studio Code 1.146 on November 11, 2026. It followed version 1.145, which shipped on November 4, 2026. If you already have VS Code installed, use Check for Updates to get it.

What is the Local harness, and when is it removed?

The Local harness is the older software that coordinates the model, context and tools for Copilot agent sessions in VS Code. Version 1.146 deprecates it, and it will be removed in February 2027. The Copilot harness replaces it.

Does the Copilot harness send my files to the cloud?

No. GitHub's changelog says choosing the Copilot harness does not move your files to the cloud. You keep working in VS Code and running agent commands on your machine.

How do I open a chat in its own window in VS Code?

Enable sessions.chatWindows.enabled in Stable (it is on by default in Insiders). Then right-click a session or chat in the sessions list and select Open in > New Window, or drag the chat out of the Agents window.

Do I need a paid Copilot plan for the Copilot harness?

No specific paid plan is required to switch harnesses. GitHub says you can keep your existing plan, including Copilot Free. Individual features and Copilot Fusion tiers depend on your plan, settings and organization policy.

Sources

Featured image: Visual Studio Code icon, public domain (trademarked), via Wikimedia Commons. Visual Studio Code is a trademark of Microsoft Corporation. FreeAnswers is not affiliated with Microsoft.

Related answers

Leave a Comment