Amp introduced Spaces in a blog post on 6 November 2026. Until now, Amp users have created and organised threads – individual conversations with an agent – themselves.

In Spaces, the user opens a workspace (a space) and talks to a single agent there. The user tells the agent what needs doing. The agent spawns the agents it needs, each in its own thread, and coordinates them. This lets the user see the work as a whole and still drill into the details of an individual thread when needed, the company said.

Amp says it has used spaces for a few weeks. The company thinks this may be how agents are used in future. It bases this assessment on its own use, and the examples in the blog post also come from its own work.

In one example, Amp employee Will gave a space a goal: review recent changes for security issues. On its first run, the agent split the codebase into 16 areas and reviewed each area in its own thread. Every finding was then checked in a separate thread. The agent kept a summary in the space for Will to review and track. The blog post does not say what the review found.

Another employee, Lewis, ran the launch of service accounts from a single space. From the space, Lewis rolled out the feature to users, monitored X, Slack and bug reports, fixed bugs and sent emails and refunds to affected users. The space tracked user issues and system status for the rest of the week.

Several people can use the same space. Amp’s team built Spaces in a shared space. Team members logged feedback, bugs and ideas in its conversation, and the agent sorted them into threads. Team members talked to each other in comments and brought in Amp’s agent when they were ready. The team started holding its conversations and video calls in the space instead of Slack, the company said.

To create a space, the user clicks the plus button in the Spaces section of Amp’s sidebar, gives the space a title and a project, and then tells the agent what to do.