Amp Spaces

What Amp Spaces is

Amp launched spaces as a new way to interact with agents and your team. A space is a conversation with a single agent whose job is to spawn and coordinate agents for you. That makes it a higher-level way to work with many agents rather than a place where you manage each thread by hand.

The practical difference is who does the organizing. In a space, you no longer have to create and organize threads yourself, because the agent in the space does it for you. You describe what needs to happen, and the coordinating agent decides how to split the work into threads.

• A space is one conversation with a coordinating agent.
• That agent spawns and coordinates other agents on your behalf.
• You do not have to create or organize threads yourself.
• Amp positions spaces as a higher-level way to work with many agents.

How a space differs from working thread by thread

Working with individual threads puts the coordination burden on you: you decide how many threads to open, what each one covers, and how their results fit together. A space moves that decision to the agent. You stay in one conversation, and the agent delegates work into threads as it sees fit.

This does not mean threads disappear. Threads are still where the delegated work happens; the space is the layer above them that keeps the overall effort in one place. Amp frames this as a new, higher-level way to work with many agents.

• You coordinate threads manually in a thread-by-thread workflow.
• In a space, the agent handles thread creation and organization.
• Threads remain the unit of delegated work beneath the space.

How to start a space

Starting a space is deliberately short. Use the + in the Spaces section of the sidebar, set a title and a project, and then tell your agent what to work on. From there, the coordinating agent takes over the job of splitting the work into threads.

• Open the Spaces section in the sidebar.
• Click the + to create a new space.
• Set a title and choose a project.
• Tell the agent what you want it to work on.

Example use cases from Amp

Amp shared two concrete examples that show how the coordinating agent behaves. In the "Spaces v1" example, Tim, Lewis, Nicolay and the rest of the team shared one space, dropped feedback, bugs and new ideas into the chat, and the agent delegated them into threads.

In a security review example, the space's first run split the codebase into 16 areas and reviewed each in its own thread, checked every finding in another thread, and kept a summary artifact in the space for Will to review and track. Together these illustrate two patterns: triaging incoming items into threads, and fanning a large review out across many threads while keeping a summary in the space.

• Team triage: feedback, bugs and new ideas dropped into chat are delegated into threads.
• Large review: a codebase split into 16 areas, each reviewed in its own thread.
• Verification: findings checked in another thread.
• Tracking: a summary artifact kept in the space for review.

Limits and pricing status

The source material describes what spaces do and how to start one, but it does not document usage limits, quotas, or pricing for spaces. Those details should be treated as unknown here rather than assumed. Amp's own documentation and release notes are the right place to confirm current limits and pricing before relying on spaces in a production workflow.

• Documented: what a space is, how the agent coordinates threads, and how to create one.
• Not documented in the source: usage limits, quotas, and pricing.
• Check Amp's official documentation for current limits and pricing.

How this launch fits into working with Amp

Spaces are an addition to how you interact with agents in Amp, not a replacement for the underlying thread model. The launch is notable because it shifts coordination from the user to an agent, which matters most when work naturally splits into many parallel pieces.

Amp is candid that this is an early position: after using spaces for the past few weeks, it says it thinks this might be the future of interacting with agents. Treat that as the vendor's own assessment rather than a measured result, and evaluate spaces against your own workflows.

• Spaces add a coordination layer above threads.
• The biggest benefit appears when work splits into many parallel pieces.
• Amp's "future of interacting with agents" framing is the vendor's own view.

Questions