Spaces
Amp introduced spaces: a single conversation with an agent whose job is to spawn and coordinate other agents, so you stop organising threads by hand. The company says its own team now builds features, runs launches and does security reviews from inside spaces.
Key points
- A space is one conversation whose agent spawns and coordinates subagent threads for you instead of you managing threads by hand.
- You create a space with + in the Spaces section of the sidebar, then set a title and a project before telling the agent what to work on.
- It is meant to be run at a bird's-eye level: you watch overall progress and open a single thread only when you need detail.
- Amp's team shipped the feature from inside a space, dropping feedback, bugs and ideas in chat while the agent turned them into tasks.
- One space can carry an ongoing job: a service accounts launch was run, supported and monitored from a single space.
- Security review parallelises well: 16 codebase areas reviewed in separate threads with findings checked by another thread and a shared summary.
Amp launched spaces, a shared workspace where one coordinating agent creates and manages subagent threads on your behalf. Instead of opening and tracking threads yourself, you state the goal inside the space and the agent splits the work and reports back, so you can stay at a high level and drop into a single thread when something needs attention.
Amp's team built the feature itself inside one space, mixing human comments with agent-delegated tasks. They ran a service accounts launch from a space while watching Slack and X reports, fixing incoming bugs and handling refunds, and gave another space a security-review goal that divided the codebase into 16 areas, reviewed each in its own thread and verified findings before keeping a summary. Start one with + in the Spaces sidebar section, set a title and a project.
Real-world use
- Rolling out a new feature and supporting it: pushing the release, watching Slack, X and bug reports, shipping fixes and issuing refunds from one space.
- A recurring security review on a large repository where the work is split by area and every finding is verified independently before it reaches you.
- A small team building a feature together: teammates leave comments and bugs in the space, the agent fans them out into threads, Amp is tagged when a decision is needed.
- Long-running operational chores such as monitoring user issues and system health for a week after a launch instead of keeping a tab open yourself.
Why it matters
The unit of work shifts from a thread you babysit to a goal you delegate, which makes many parallel agents practical for launches, reviews and support without the bookkeeping of tracking each one.