Microsoft Releases VS Code 1.145 With Agent Tools
The stable update focuses on agent workflows, adding remote browser and canvas support, local automations, and finer chat session controls.
Updated on Nov. 4, 2026 in Remote Work
Microsoft released Visual Studio Code 1.145 on November 4, 2026. The update centers on agent workflows, including remote browser and canvas support and more flexible local automations.
Why it matters
The release gives developers new ways to review and direct AI agent work inside the editor. Expanded chat session controls and file-exclusion settings give users more say over how agents behave and what they can see.
The stable build is version 1.145, released November 4, 2026. Remote canvases remain in preview, and the extraction gives no adoption or usage figures for the new agent features.
The players
Microsoft
Microsoft is the technology company that develops and publishes Visual Studio Code, a widely used code editor.
The details
The release adds the workbench.browser.enableRemoteProxy setting, which loads browser pages through a remote agent host, so developers can open a remote dev server preview in the integrated browser. Nested sessions let a second agent review work using a different harness, while each nested chat keeps its own model, agent, and permission settings.
Timeline
November 4, 2026: Visual Studio Code 1.145 stable release becomes available.
Remote Work
The 1.145 update extends the agent and chat features that Visual Studio Code has been building out, adding remote browser access and nested sessions. Those additions let developers run and review agent work from remote environments rather than only inside the local editor window.
Developers can open remote dev server previews in the integrated browser and use nested sessions to get a second agent to review their work without leaving the conversation. Per-chat model, agent, and permission settings let users control how each session behaves.
The takeaway
Developers who rely on agent-assisted coding can use nested sessions and per-chat permission settings to keep reviews separate from main work. Testing the remote proxy setting early can show whether remote previews fit an existing workflow.
Further reading
Explore more on Remote Work to see how developer tools like this are changing where and how software gets built.
