Visual Studio Code 1.134 Ships with Dedicated Agent Host Process and Grid Chat Layouts
The August 19 release moves AI agents out of the extension host, adds multi-window session sharing, and polishes the editor with a few long-requested UX tweaks.
Visual Studio Code 1.134 is out, and if you've been tracking how Microsoft plans to keep its editor relevant as agentic AI tools multiply, this is the first real signal. Released today, the update pulls long-running AI agent work out of the extension host and into a dedicated, standalone process. It also gives you a grid layout for side-by-side chats, a prompt timeline, and a few long-requested editor conveniences.
For years, Copilot and third-party agents have lived side by side with your linters, formatters, and language servers in VS Code's extension host. That works fine until an agent needs to run across multiple windows, survive a refresh, or hand off work to another machine. The extension host just isn't built for that.
The Agent Host Process Changes Everything (Sort of)
Microsoft's new Agent Host runs as a local utility process by default, communicating with VS Code over message ports. You can also run it as a standalone server exposed via SSH or a dev tunnel, with clients talking over WebSocket using the new Agent Host Protocol (AHP). The protocol is open, agent-agnostic, and uses JSON-RPC with immutable state. Hit the network, lose the connection, reconnect later, and the client pulls back the missed actions or a fresh snapshot.
What actually shifts for you? Multiple editor windows can now share a single agent session. You can monitor an agent running on a remote machine. Close the window, come back tomorrow, and the session is still there. Different adapters, including Copilot, Claude, and Codex, plug into the same host-facing interface without fighting for extension host resources.
Legacy agent sessions still run in the extension host, but they're functionally older. No multi-window sharing. No remote hosting. No shared chats per session. If you're not already using the Agent Host, you'll probably start noticing the gap pretty quickly.
Grid Layouts, Timelines, and Editor Polish
The headline UX change is the chat grid. You can now drag conversations and subagent chats into horizontal or vertical groups. Compare two refactoring approaches side by side without tab hell. Alt-click a chat in the picker to open it beside the current one. VS Code remembers the layout across reloads.
Long sessions get a prompt timeline in the transcript gutter. Each dot marks a prompt. Hover for a summary. Click to jump. If a prompt changed files, you get added and removed line counts, plus a direct link to review the diff. Search the full conversation with ⌘F or Ctrl+F, and collapsed work summaries expand if they contain the match.
The side pane gets a single-pane detail mode that actually respects workbench.editor.showTabs, with file breadcrumbs in the header. Hold Alt while hovering an editor tab and the close action flips to "Close Other Editors." It's a tiny tweak, but community contributor jadefr pushed it through after years of requests. Simon Siefke also quietly fixed seven memory leaks across the extensions view, source control, code actions, search, and chat widgets. Not exactly headline material, but the kind of maintenance that keeps the editor from feeling heavier every month.
The release page links to "VS Code Live at MS Build 2026," which tells you exactly where this fits in Microsoft's roadmap. The AHP spec is deliberately locked to no single vendor, remote execution is baked in from day one, and extensions still get to contribute tools and MCP servers. They just don't own the runtime anymore. It's a clean break from the chat-completion era and an explicit bet on autonomous coding assistants.
Is it perfect yet? Agent workflows are still early enough that the learning curve is real. The legacy extension-host behavior will stick around for a while, which means you'll occasionally see feature gaps depending on how your agents are configured. Running a dedicated process for every active agent session does mean more background memory usage if you keep a lot of them open. Still, the architectural foundation is exactly what VS Code needed as the editor becomes a control plane rather than just a text box.
Head here to download the update. Windows ships as x64 and Arm64, macOS as universal and silicon DMGs, and Linux gets deb, rpm, tarball, and snap builds across x64 and Arm. If you're already running agentic workflows, you'll want to test the Agent Host alongside your existing adapters. The rest of us get to watch how the protocol evolves in public.
