Agent Upstart

Cool things people are building with agents — and practical help getting the most out of them.

Playbooks · Coding tasks

VS Code 1.145: Agent Host keeps sessions alive

Written November 9, 2026

VS Code 1.145 (Nov 4) runs agent sessions in the Agent Host, so they keep going in the background. Plus mixed agent setups, cron, and Fusion's 30% discount.

What the Agent Host changes

Before this release, an agent session belonged to the editor window that started it. In VS Code 1.145, released November 4, 2026, sessions run through the Agent Host, a separate process from the editor. Copilot sessions keep running in the background, and you can reach them from both the editor window and the Agents window. Close the window, and the session does not go with it.

The Copilot harness stays the default for new sessions in VS Code. It is built on the Copilot SDK, the shared base GitHub uses across Copilot products. If your team still runs the Local setup, the release notes point to a Local-to-Copilot harness transition guide covering customization compatibility, session continuity, and rollout checks.

Verdict: if you run long agent sessions, update for the continuity alone. A session that survives a closed window is the difference between an agent you trust with a half-hour task and one you babysit.

What else shipped in 1.145

Mixed agent setups in one session (preview). Nested sessions can now use a different agent setup than their parent, behind the chat.agentHost.multipleChatProviders.enabled setting. Ask Claude to review a plan a Copilot chat wrote, or give Codex the same task, side by side in the same session. Each chat keeps its own model, agent, and permission levels.

Remote agent sessions feel local (preview). The integrated browser in the Agents window now loads pages through a remote agent host, so a dev server started by an agent on a remote machine opens inside the editor. Remote canvases work the same way, behind chat.canvases.enabled and workbench.browser.enableRemoteProxy.

Cron schedules for local automations. Local automations accept a five-field cron expression when the built-in presets are not precise enough. The dialog validates the expression and describes the schedule. Cron schedules are not available for cloud automations.

Chat verbosity (experimental). Three view modes — Conversation, Verbose, and Compact — change how reasoning and tool calls display, not the work the agent performs.

Managed MCP allowlists. For MCP servers VS Code starts, the enterprise-managed allowedMcpServers list now takes precedence over registry-only access. A listed server runs even if it is not in the registry; an unlisted registry server is blocked; an empty list blocks everything. This covers servers VS Code starts, not servers managed by the Agent Host.

The Local setup lost three tools. Install Extension, Run VS Code Command, and Create New Workspace are gone from Local agent sessions. If your custom agents or prompt files reference #installExtension, #runCommand, or #newWorkspace, remove those references.

The money line: Fusion is 30% off until November 30

Copilot Fusion, the router that picks models for a task instead of making you pick one, is generally available. GitHub's docs say paid Copilot plans get a 30% discount on model costs when using Fusion through November 30, 2026, with no separate Fusion fee — you pay for each model it uses at that model's standard rate. Measure any cost baseline before that date, because the same usage costs more in December.

Limits

Related playbooks

Sources

Back to: Coding playbooks hub · Also: Run your own agent bake-off on one real task · Copilot Fusion is generally available: what it does to your AI-credit bill · Copilot CLI 1.0.106: /code, /settings, GPT-6.1 Terra