Surfaces
Pattern 22 of 26
Multi-Agent Workspaces
A control room for your agents
Multiple agents working on a shared project is powerful and, without a workspace, almost impossible to follow. Multi-agent workspaces give each agent persistent identity, shared state, and a visible interface so the human in the loop can actually see what is happening. VS Code called itself a multi-agent platform in January 2026. That framing was not accidental.
Why it matters
Multi-agent orchestration is invisible by default. You get outputs but not reasoning. Workspaces make the operation legible. You can see what each agent is doing, catch errors before they compound, and step in without stopping everything.
Deep Dive
Running multiple agents in parallel on a shared task is one of the more interesting things you can do with current models. It is also one of the harder things to manage. Without visibility into what each agent is doing, you are just waiting for outputs to arrive and hoping they fit together. Workspaces solve the visibility problem. VS Code v1.109, released in January 2026, is the most prominent example: it explicitly positioned itself as a multi-agent development platform, not just a code editor with AI features. Claude Code Agent Teams is still experimental but points in the same direction.
The enterprise version of this is something like Dust: multiple specialised agents with different tool access and permission scopes operating on shared company knowledge. Each agent knows what it has access to. The workspace surfaces that structure. CrewAI Cloud is similar as a managed service. The design challenge that every one of these systems runs into is legibility. When three agents are working simultaneously on related subtasks, the workspace has to surface enough context for a human to oversee without making them micro-manage. Getting that balance right is harder than it looks.
My current working theory is that IDEs are becoming the default multi-agent workspace for developers, and that the editor evolves rather than gets replaced by something purpose-built for orchestration. The 2026 releases from VS Code suggest Microsoft agrees. The developer role is shifting from writing code line by line to coordinating agents working in parallel on a shared codebase. The workspace is how that coordination becomes something you can actually manage. Whether it ends up looking more like a code editor with agent panels or a project management tool with code attached is still genuinely open.