SATURDAY, NOVEMBER 21, 2026 Tech news, minus the noise.
N News Cast
LATEST
Software

VS Code 1.147 Brings Browser Use, Model Routers and Send-Later to the Stable Channel

VS Code 1.147 reached stable on November 18 with Browser Use, Model Routers, and Send-Later, continuing Microsoft's steady rebuild of the editor around AI agents.

VS Code 1.147 Brings Browser Use, Model Routers and Send-Later to the Stable Channel
Source: Markus Spiske, CC0, via Wikimedia Commons

VS Code 1.147: browser use, model routers, and send-later

Visual Studio Code 1.147 reached the stable channel on November 18, and it continues the direction Microsoft has been pushing all year: the editor is becoming a place where AI agents do real work, and the new features are about managing those agents rather than showing off a single capability. The headline items are Browser Use, Model Routers, and Send-Later, three features that sound small on their own and add up to a meaningful change in how the editor treats agent sessions.

Browser Use gives an agent the ability to use a browser as part of its work, which matters because so much of development now involves reading documentation, checking a live site, or verifying a fix in a real page. An agent that can only read your code is limited. One that can open a browser, look at the thing it just changed, and tell you whether it worked is doing the job you actually hired it for.

Model Routers address a different problem: choosing which model should handle a task. As the model menu keeps growing, picking the right one for each job has become a chore of its own. A router makes that choice for you, sending a task to the model best suited to it, and the VS Code 1.147 update brings that routing into the editor's agent workflow. Send-Later, the third headline item, lets you schedule messages to an agent, so you can queue up work for a session that is busy or offline and have it picked up when the session is ready.

A fast follow to the 1.146 release

The 1.147 update arrives a week after VS Code 1.146, and the two releases read as a pair. Version 1.146 added the agent Inbox, a consolidated view of every session that needs your attention, and started the countdown to removing the Local agent harness in February 2027. Version 1.147 adds the tools that make those sessions more capable: a browser to look at things, a router to pick the right model, and a way to schedule work.

The pattern is worth noticing. Microsoft is shipping the agent features in small, weekly steps rather than saving them for a big launch, and each step removes one piece of friction from the agent workflow. The Inbox solved the problem of losing track of sessions. Browser Use solves the problem of an agent that cannot see the result of its own work. Model Routers solve the problem of choosing between a dozen models. None of these is a marquee feature on its own, and together they are the reason the agent workflow is starting to feel usable rather than experimental.

The security thread continues

The 1.146 release also tightened security around agent sessions, with more granular permission prompts and a setting to mask environment variables inside sandboxed sessions. That matters because agents with browser access and model routing are more powerful than agents without them, and more powerful agents need tighter limits on what they can touch. The Copilot harness, which runs sessions through the Agent Host with managed sandbox policies, has been the default since VS Code 1.143 in October, and the Local harness it replaces goes away entirely in February 2027.

If you are still on the Local harness, the message from Microsoft has not changed: start planning the move. Three months was the window when 1.146 shipped, and it is shorter now. Test your workflows against the Copilot harness while both still work, and check whether anything you rely on depends on Local harness behavior.

What to do this week

Install the update, then look at the three headline features in the order that matches how you work. If you run agents that need to check their work against a live site, Browser Use is the one to try first. If you spend time picking models for each task, Model Routers will save you the most clicks. And if you work with agents across time zones, or you queue work for the morning, Send-Later is the small quality-of-life feature that will quietly become a habit.

As with the 1.146 release, the new features are off by default or tucked behind settings, so nothing changes until you turn them on. That is the right approach for an editor that millions of people rely on for their daily work. The agent features are arriving steadily, one release at a time, and the editor is being rebuilt around them without breaking the thing it already is. For the wider tooling picture, the background MCP tasks that Claude Code gained recently and the Chrome DevTools MCP agent tools show the same pattern across the ecosystem: the agent is becoming a first-class citizen in every tool developers use.

AS
News Cast Editorial Team

We cover AI, gadgets, startups and security — original reporting and explainers, written by humans, for humans. Got a tip? Reach us via the contact page.