On November 6, 2026, coding agent Amp launched spaces, a new way to work with agents and your team. A space is a conversation with a single agent whose job is to spawn and coordinate other agent threads for you, so you no longer have to create and organize threads yourself. Amp's bet is that this may be the future of working with agents: the human sits in the 'captain's chair' with a bird's-eye view, diving into the details only when needed.
Amp illustrates it with three examples from its own team. Building a new feature, the whole team shared one space called 'Spaces v1', dropping feedback, bugs, and new ideas into the chat while the agent delegated them into threads; when they wanted to talk, they chatted in comments first and tagged in Amp when ready. Running a launch, Lewis shipped the service accounts feature from one space: monitoring X, Slack, and bug reports, fixing incoming bugs, and sending out emails and refunds — and the space kept watching user issues and system health for the rest of the week. Running regular security reviews, Will gave a space a goal: review recent changes for security issues; its first run split the codebase into 16 areas, reviewed each in its own thread, cross-checked every finding in another, and filed 14 issues into a summary document kept in the space.
Starting a space is simple: hit + in the Spaces section of the sidebar, set a title and a project, then tell your agent what to work on. Amp also notes that over the past few weeks the team naturally moved its discussions into spaces, even replacing Slack with video calls and conversations held there. But this is still Amp's own usage: teams differ in size and process, so whether the effect transfers will only become clear once more teams have tried it. And parallel multi-agent work is not free — multi-agent team tests show costs rising as much as 5.1× while quality barely moves; spaces save the time spent organizing threads, but the cost of coordination itself does not disappear.
Two things are worth watching next: whether spaces grow from an Amp feature into a general way of working with multiple agents, and whether other coding tools follow with similar designs. Meta's acquisition of Conductor, betting on parallel multi-agent coding, already shows the big players moving in the same direction. For teams already using Amp, trying it costs little — open a space for the next feature and see whether it saves thread-organizing time, or adds another layer of coordination to watch.
