Microsoft Decouples AI Agents From the VS Code Editor in Latest Release

Sicherheitsmeldung mit Schweregrad noch nicht bewertet. Technische Details im Tab „Originaltext“; empfohlene Schritte in der Checkliste.

Originaltext der Quelle (nicht übersetzt) – die deutsche Zusammenfassung findest du im Tab „Kurzfassung".

Microsoft has shipped Visual Studio Code 1.133, and the headline change is architectural rather than cosmetic: AI agent sessions now run in a dedicated background process rather than within the editor’s extension host. The release, which rolled out August 12, moves agent execution into what Microsoft calls the Agent Host, a standalone process built on a new open specification: the Agent Host Protocol (AHP). Microsoft published the AHP spec on GitHub under an MIT license, positioning it alongside the Language Server Protocol (LSP) and Debug Adapter Protocol (DAP) as infrastructure other tools can build on, not just a VS Code implementation detail. The practical effect for developers is that an agent session no longer has to live and die with a single editor window. Because the host runs independently, multiple VS Code windows can connect to the same session and see a synchronized view. The protocol uses JSON-RPC, immutable state, and pure reducers to keep clients in sync, with each state change carrying a sequence number so nothing arrives out of order. Sessions can also run remotely, reached over SSH or a dev tunnel, which matters for teams running agents against machines that aren’t sitting on a developer’s desk. “Moving agent sessions into a standalone host lets a developer reconnect to a running session from another window or over SSH. The agent no longer dies when one editor closes. It starts behaving like shared infrastructure,” said Mitch Ashley, VP and practice lead, Software Lifecycle Engineering and AI-Native Software Engineering, for The Futurum Group. Microsoft …

Vollständiger Originalartikel ↗

• Betroffenheit im eigenen Stack prüfen: Versionen/Komponenten abgleichen.
• Originalquelle / Hersteller-Advisory lesen: https://devops.com/microsoft-decouples-ai-agents-from-the-vs-code-editor-in-latest-release/
• Verfügbaren Patch oder Workaround einspielen und dokumentieren.