Visual Studio Code 1.147 Lands on Stable With Browser Use, Model Routers, and a Send-Later Button
Microsoft doubles down on its agent strategy, though much of the good work still hides behind opt-in switches.
Visual Studio Code 1.147 is on stable now. Microsoft shipped it today as version 1.147.0, and it's a feature-packed week that leans hard into making the editor's AI agents more flexible, more visual, and easier to govern. The headline tools are browser use, automatic model routing, a send-later scheduler, saved drafts, and inline chart previews. There's also a fix IT admins have wanted for a while.
That fix is arguably the most durable part of the release. But first, the toys.
Agents get a real browser, a scheduler, and smarter routing
The flashiest new capability lets an agent drive your actual Chrome or Edge browser instead of working only inside VS Code's walls. Microsoft calls it Browser Use, and it's in Preview. The agent reuses an authenticated session, so it can click through pages as you, beyond the editor. That's a meaningful step up from chat-only automation.
The setup is the friction. You need the GitHub Copilot browser extension, a local Copilot session running on your machine, and Node.js 22 or newer. Then you flip chat.agentHost.browserUse.enabled, run /plugin enable browser-use, approve site access yourself, and finally /browser-use:doctor to confirm it's working. Not a one-tap affair.
Model routers solve a different problem. A router is just a YAML file that maps kinds of work to specific models, and a decision model matches each incoming request to the right route. It's a switchboard that picks the cheapest model for a quick question while saving the frontier model for heavy lifting.
The release notes show a route that sends building-code tasks to Opus and quick questions to "GPT-6 Luna." Microsoft flags that routers are early-stage and is openly asking for feedback on GitHub. The payoff is real, though: teams stop hand-picking a model for every single prompt.
Send Later and drafts are the quieter wins, and both are worth keeping in mind. The former lets you schedule a chat request for a specific time, either through a menu on the send button or by telling the agent to "check the build in 10 minutes." Drafts used to hold just one unsent request. Now you can keep several around, each with its own workspace and attachments, and they survive reloads.
Keep in mind that scheduling won't wake a sleeping laptop. The local agent host has to be running at the scheduled moment, or the request just waits its turn. Scheduled requests also need automations enabled and only apply to sessions on this computer.
Visuals round out the agent experience. New skills let agents render inline HTML and theme-matched bar charts or badges right inside replies, so reports and model comparisons become something to look at rather than only read.
A real governance fix, plus housekeeping
Here's the part that matters for most shops. Microsoft now lets admins permit Claude and Codex alongside Copilot's managed settings. Previously, any Copilot enterprise policy disabled those alternatives, forcing a choice between governing Copilot and offering something else. A new setting, vscode.allowedHarnesses, takes both on now. Enter claude or codex and they're allowed; an empty list blocks both.
It isn't a silver bullet. Claude and Codex still run without Copilot's sandbox, MCP, and plugin controls, so they aren't fully governed the way Copilot is. Server-managed settings don't support the new option yet. But at least acknowledging the alternatives resolves a nagging enterprise complaint.
On top of that, managed shell permission rules now accept JavaScript regular expressions. That means you can require approval for anything starting with git push while letting everything else run. Small, but precise.
The housekeeping is where support ends. VS Code 1.147 drops macOS Ventura and Sonoma, retires 32-bit ARM Linux, and removes a low-usage AI stats status bar setting. The Local agent harness is now fully deprecated, with removal slated for February 2027. Microsoft is consolidating around its built-in Copilot backend.
If you've lost count of the version numbers, this is why. VS Code moved from monthly to weekly stable releases starting with 1.111 in March 2026. In the weeks leading up to 1.147, builds landed seven days apart: 1.145 on November 4, 1.146 on November 11, and now this one. Each week bundles a smaller, still-meaningful set of changes rather than one big monthly dump.
For managed fleets, the advice stays familiar: wait for the first patch and read the parent release notes before rolling out.
Our take: it's a strong week on paper. Browser use, routing, and scheduling are the pieces an agent workflow actually needs, and the governance fix is the one that'll stick. Everything else is Microsoft still calibrating, which is fair given how recently the agent battle turned into a full one against Cursor, Windsurf, and Claude Code.
The recurring caveat is that you enable most of this via experimental settings, or stay on Insiders if you want to try it earlier. The stable core, by contrast, is just reliable edits.
Head here to the official release notes to read the full changelog and decide what's worth flipping on.
