VS Code runs agents over SSH

On May 20, Microsoft shipped Visual Studio Code 1.121 with a new remote-agents feature: agent sessions can run on a remote machine and be monitored or controlled from VS Code’s Agents window. The company described it in the official release notes as the ability to “run agent sessions on remote machines.” (code.visualstudio.com) The practical change is simple: the agent no longer has to run on the same machine as the editor. Developers can point VS Code at a box they already reach over SSH, let the tool start its remote components there, and then interact with that session from the local client. ByteIota reported that VS Code can also work through dev tunnels and auto-installs its CLI on the remote host. (byteiota.com) What makes this more than a convenience feature is the session model. ByteIota said the underlying Agent Host Protocol, or AHP, is being built as an open standard and is designed for “multi-client state coordination,” meaning multiple VS Code windows or third-party clients can attach to the same agent session and see synchronized state. Microsoft has separately framed VS Code’s broader direction this year as “multi-agent development,” with session management spanning local, background and cloud contexts. (byteiota.com) That architecture pushes familiar backend problems into the editor. Once one remote agent session can be shared across clients, the hard questions become the ones infrastructure teams already know: who is allowed to attach, how state stays consistent, what happens when two clients issue conflicting actions, and how command execution is audited on a remote machine. Those implications are an inference from Microsoft’s release notes and ByteIota’s description of synchronized multi-client sessions, rather than a separate Microsoft statement spelling each one out. (code.visualstudio.com) It also fits Microsoft’s larger product direction. In February, the VS Code team said it wanted the editor to be “one place to run your agents, manage your sessions, and pick the right tool for each task,” and the January 2026 release had already emphasized agent session management across local, background and cloud environments. The new SSH-based remote session support extends that push into standard developer infrastructure instead of keeping agent execution tied to a local workstation. (code.visualstudio.com) For developers, the appeal is straightforward. Remote execution lets an agent run closer to the codebase, build tools or compute resources it needs, while the local VS Code window becomes more of a control surface. For teams and tool builders, the notable part is that Microsoft appears to be treating agent sessions as shared, attachable runtime objects rather than one-editor, one-process interactions. That reading is based on the release notes and the AHP description cited above. (code.visualstudio.com) The feature arrived in VS Code 1.121, released May 20, 2026, and is documented in Microsoft’s release notes. GitHub’s releases page lists 1.121.0 as the latest tagged VS Code release as of May 24. (code.visualstudio.com)