On 2026-11-06 Amp (ampcode.com) launched Spaces: a Space is a conversation with one orchestrator agent that understands a goal, decomposes work, and creates/coordinates parallel threads so users need not manage threads by hand. Official examples include co-building a feature, running a service-accounts launch, and a security review split across 16 areas. Start from the Spaces sidebar with + (title + project); teammates comment in the same chat, and Amp reads comments only when @-mentioned.
Key Takeaways
- ✓Official: ampcode.com/news/spaces (2026-11-06); Amp teammate Lewis Metcalf posted; @AmpCode amplified
- ✓Form: one orchestrator agent decomposes goals, spawns parallel threads, and summarizes; bird's-eye or deep dive
- ✓Teams: comment inside the same Space; Amp reads comments only when @-mentioned
- ✓Examples: Spaces was built inside a Spaces v1 room; service-accounts launch ops; security review across 16 areas
- ✓Start: Spaces sidebar → + → set title and project → describe the goal
Key Decision Metrics at a Glance
Turn your technical choice into a development budget
Compare 40 dev plans & simulate token costs vs $20/mo subscriptions
Project Links & Resources
Direct AccessIn-Depth Technical Analysis
Core Background & Industry Pain Points
Multi-agent coding often forces users to create, name, assign, and track threads themselves while bouncing between Slack and the IDE. Amp argues for a higher-level mode: state a goal and let an orchestrator agent decompose and parallelize the work.
Architecture Highlights & Internals
A Space is a long conversation with one orchestrator agent. It breaks the goal into concrete tasks, spawns parallel worker threads, and shows progress as cards; clicking a card opens that thread. The design keeps a captain's-chair overview with optional deep dives. Team comments live in the Space; Amp reads them only when @-mentioned to cut noise.
Authoritative Benchmarks & Measured Scores
Amp published no standalone benchmark or leaderboard. Public evidence is product narrative plus internal cases: Spaces was co-built inside a Spaces v1 room; Lewis ran a service-accounts launch from one Space while watching X/Slack/bugs; Will's security review first split the codebase into 16 areas, reviewed findings in further threads, and kept a summary artifact. Numeric claims: not published by the vendor.
Developer Hands-on Guide
In Amp, open Spaces in the sidebar, click +, set a title and project, then describe the goal (e.g., review recent changes for security issues, or ship a feature). Fit for multiplayer co-creation and multi-day ops; agree who may @amp and which threads need human gates before production. Details: ampcode.com/news/spaces.
Benchmark side-by-side against alternatives, or calculate monthly token cost vs subscription break-even.
Discussion & Comments
0Sign in to join the discussion
Connect with AI developers to exchange benchmark insights.