VS Code 1.145: Coding Agents That Work While You Sleep
VS Code 1.145 shipped November 4, 2026, turning the editor into an agent host: remote agents you can preview in the Agents window, automations on a five-field cron schedule, and nested sessions that mix harnesses. What changed, what is still preview, and the four moves to set it up today.
Amir Ali Liaqat · Founder & CEO, DesignsToDeploy

On November 4, 2026, Microsoft shipped Visual Studio Code 1.145, a stable release that keeps moving the editor in one direction: away from a single chat box and toward a persistent agent host. The release notes lead with five things: remote agents that feel local, automations on a cron schedule, chat verbosity controls, file exclusions, and a small platform game starring Blobby, the VS Code pet. The first four are the story. The game is a reminder that the team shipping all this still has a sense of humor.
The shift underneath is the one to understand. A year ago, the editor helped you write code line by line. Now it runs agents that edit files, run tools, and carry work through a whole workflow, and the 1.145 release is mostly about making those agents easier to run, schedule, and supervise. None of it removes the developer. It moves the developer up one level, from typing every change to directing and reviewing.
Remote agents that feel local
The headline change is for anyone whose agents run somewhere else. 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, and give it feedback, exactly as you would in a local session. Remote canvases work the same way, so interactive agent output hosted remotely renders inside the editor. Both are in Preview, behind the workbench.browser.enableRemoteProxy setting, with canvases also needing chat.canvases.enabled, and Microsoft is asking testers to file issues as they try them.
For teams, this closes a real gap. Remote work used to mean switching to a separate browser to see what the agent built, which broke the review loop. Keeping the preview inside the Agents window keeps the loop tight: the agent changes something, you see it, you tell the agent what is wrong, all in one place.
Automations on a cron schedule
The second change is the one with the best hook. VS Code automations already let you schedule agent tasks to run automatically, on demand or on a set schedule, instead of running them one by one by hand. Version 1.145 adds five-field cron expressions for local automations, for when the built-in schedule presets are not precise enough. Pick Cron, enter the expression, and the dialog validates it and describes the resulting schedule in plain language. Two honest limits: cron schedules are not available for cloud automations, and this release also lets you pick a workspace custom agent when creating or editing a local automation, while disabled automations collapse into their own section so they stop obscuring active work.
This builds on the October 28 release, 1.144, which introduced persistent sessions through the Agent Host, so agent work can continue in the cloud even after you shut down your PC, with a paid Copilot plan and subject to organization policies. Copilot Fusion, which picks the model, reasoning effort, and execution pattern for a request, went generally available in the same release. Put the two releases together and the direction is clear: the editor is becoming a place where work is scheduled, handed off, and picked up again, not only typed.
One session, more than one harness
The third change is the most interesting for anyone who has ever wanted a second opinion. Nested sessions let you keep related conversations together inside a single main chat session. Until now, every nested session inherited its parent session's harness, so getting a second agent's view meant starting a separate session and losing the grouping. In 1.145, nested sessions can use a different harness from the parent. Microsoft's own example: ask Claude to review the plan that 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, and moving a chat keeps its history and its harness. The feature is in Preview, behind chat.agentHost.multipleChatProviders.enabled.
“The editor stopped being a chat box. It became an agent host. The job now is directing and reviewing, not typing every change.”
Quieter chats, too
The rest of the release is about control. Chat verbosity is now a choice, in Preview: open the Chat view's More Actions menu and pick a View Mode. Conversation groups reasoning and tool calls into collapsed sections, Verbose follows each step with tool calls expanded, and Compact, the default, previews tool calls while they run and collapses finished groups into summary rows. The modes change how the conversation is displayed, not its context or the work the agent performs. You can also pin a canvas to the left sidebar, keep specific files visible inside excluded folders with a ! exception in files.exclude, and review pending agent edits in the working set, which now tracks parallel edits to the same file. The Copilot harness, built on the Copilot SDK, continues as the default for new sessions, and its sessions keep running in the background, reachable from the editor window and the Agents window.
Set it up today, in four moves
First, update. Use Check for Updates in VS Code to reach 1.145, the stable release from November 4. Microsoft has already shipped a 1.145.1 follow-up addressing reported issues, so take the newest patch while you are there. Second, automate. Open the Automations view, pick Cron, and paste a five-field expression for one recurring task, something boring and repeatable, like a dependency check or a test run. Third, mix. Open a nested session, switch its harness, and let a second agent review the first agent's plan before you merge anything. Fourth, control. Set verbosity to Compact, pin the canvases you actually use, and exclude the folders you never want the agent to touch.
The honest part is the same as with every agent release: several of these features are Preview or Experimental, so expect rough edges, and file issues when you hit them. Cron is local automations only. Remote previews and canvases need settings switched on. And no matter how good the scheduling gets, the agent still does not ship alone. The working set exists because a human still reviews the diff. That is not a limitation to work around. It is the workflow.
Sources: Visual Studio Code 1.145 release notes, code.visualstudio.com/updates/v1_145 (November 4, 2026, Stable); Visual Studio Magazine, VS Code 1.145 Expands Remote Agent Workflows, Adds Cron Automations (November 4, 2026); Neowin, Visual Studio Code 1.145 rolling out updates to streamline agent workflows (November 4, 2026). VS Code 1.144 details as reported in its release coverage (October 28, 2026). All claims observed November 6, 2026.
1 / 5Keep reading

Git 2.56: Safer Conflicts, a Tidier Repo, and Much Faster History
Git 2.56 landed in late September 2026 with one theme: stop the small mistakes that cost teams hours. Here is what changed, from git add --resolved and branch cleanup to merge-base speedups that turn minutes into milliseconds.
Read article
Node 26 Goes LTS: Patch First, Upgrade Smart
On October 28, 2026, Node.js 26 becomes the long-term support release your production apps should run on. Five days earlier, a security release patched Node 22, 24 and 26 together. Here is the timeline, the fixes, and the safe upgrade order.
Read article
GitHub Copilot Now Works in Xcode and JetBrains Air
On November 3 and 4, 2026, GitHub put Copilot inside Xcode's built-in coding assistant and JetBrains Air. One subscription now works across the IDEs developers already use, with cloud tasks in isolated sandboxes and no new JetBrains subscription required. What changed, what it costs, and the three moves to try it this week.
Read article