Visual Studio Code 1.137 Puts AI Agents Front and Center with Voice Mode, Scheduled Tasks, and an Open Protocol
Microsoft’s latest editor update decouples agent sessions from workspaces, adds scheduled automations, and ships a portable, open protocol that lets AI workflows survive folder closures and roam across machines.
Visual Studio Code 1.137 shipped today, and Microsoft is making it unmistakably clear that the editor is no longer just a place you write code. The release rolls out scheduled agent automations, an experimental voice interface for chatting with AI while it edits your files, deeper GitHub integration inside the agents window, and a completely new architectural foundation called the Agent Host. If you’ve been following VS Code’s trajectory over the past year, the shift toward autonomous AI workflows should feel less like a sudden pivot and more like the inevitable next step.
The Architecture Behind the Scenes
The old agents window felt bolted to the editor skeleton. Close a folder, close the agent. The new Agent Host decouples that relationship entirely. Sessions now live in a dedicated background process. You can reopen later and pick up exactly where you left off. You can even point a desktop or browser instance at a remote Agent Host running over SSH or dev tunnels. It is a rather ambitious restructuring, though the portability gains are hard to ignore.
All of that runs on the open-source Agent Host Protocol (AHP), now published at microsoft.github.io/agent-host-protocol/. Microsoft describes it as state-first. Hosts translate proprietary harness events into a durable, ordered state stream that clients can optimistically apply and reconcile if you drop your connection. Client libraries are shipping for Rust, TypeScript, Kotlin, Go, and Swift. You can spin up a standalone host right now with code agent host or code-insiders agent host.
Copilot and Claude harnesses each keep their own SDKs and agent loops, but they now share the same session model through AHP adapters. The architecture blog published August 26 by Rob Lourens, Connor Peet, and Brigit Murtaugh lays out the full rationale. Keep in mind that every harness still speaks its own native language underneath, so expect some hiccups as the community ships adapters.
What You’ll Actually Use
The headline features target people already running agents regularly. Automations, currently in preview, let you schedule recurring tasks. Run them hourly, daily, weekly, or trigger them manually. Out-of-the-box templates handle routines like catching up on recent changes, triaging issues, or hunting down bugs. You can also write custom prompts and schedules. The setting lives under chat.automations.enabled and drops into the Agents window sidebar.
Voice Mode is experimental. You can talk to your agent while it works, interrupt mid-response, or redirect it with a push-to-talk shortcut. It tracks active sessions, selected models, and attached files, and can spin up new sessions on command. Org admins can disable it by turning off Copilot preview features. Not cheap in terms of background overhead, but the hands-free workflow does save time on long refactors.
GitHub integration just got noticeably tighter. Clicking a github.com issue or pull request link in any chat now opens the full details directly in the Agents window. No browser tab. No context switching. You can also attach issues and PRs as live context from the "Add Context..." menu, pulling in descriptions, comments, and diffs without pasting a single URL into a prompt.
If you start a quick chat without a workspace, you can later attach a local folder to keep that same conversation going as a proper workspace session. It keeps the title, history, and current request. The agent picks up with direct access to your files. Currently limited to the Copilot harness. Multi-agent workflows got a predictable touch too. When one agent needs to message another busy session, VS Code now queues that request instead of interrupting active processing. Messages process in order after each turn completes. It stops conversations from colliding.
The diff editor now offers a new layout option. Inline, side by side, or automatic. The automatic setting adjusts to editor width changes without bouncing content around. Binary files that changed are finally visible in multi-file diffs as a placeholder you can click into the standard diff view. GitHub links in Markdown files now render live titles and states, updating automatically when CI runs or issue statuses change. That same rendering can be enabled in chat through chat.experimental.richLinks.enabled. Microsoft also shipped the GitHub Pull Requests extension at version 0.166.0, bundling faster webview loading and making sure every github.com link in the editor opens through the extension.
The release coincides with a couple of community moments. Microsoft dropped a documentary called The Story of VS Code, tracing the editor’s history and the community that built it. You can watch it at aka.ms/the-story-of-vs-code. There is also a contest running September 10 through 17 to name an experimental VS Code pet companion that reacts as you work. Type /vscode-pet in chat to meet it, then submit your pick. GitHub Copilot Day is scheduled for tomorrow, September 10. Microsoft will cover agents, model selection, and cross-product workflows across GitHub, the Copilot app, Copilot CLI, and VS Code.
It is a substantial update, though the agent-heavy feature set skews toward power users who are already running AI workflows daily. If you are still treating Copilot like a glorified autocomplete, most of 1.137 will just feel like background noise. The Agent Host architecture is the real story here. Decoupling sessions from folders and giving them a portable, protocol-defined lifecycle is exactly the kind of shift that makes autonomous agents actually practical instead of just performative. Not everything is stable yet, and some features sit behind preview toggles, but the direction is clear.
Head here to grab Visual Studio Code 1.137. Windows x64 and Arm64, macOS Universal, Intel, and Silicon, plus Linux deb, rpm, tarball, and snap packages for x64 and Arm are all supported.
