{
  "@context": "https://schema.org",
  "@id": "https://aggr.aymericbeaumet.com/items/ampcode-com/2026-11-06-spaces/#webpage",
  "@type": [
    "WebPage",
    "ArchiveComponent"
  ],
  "articleBody": "Today we're launching spaces, a new way to interact with agents and your team in Amp.\n\nA space is a conversation with a single agent whose job is to spawn and coordinate agents for you. You no longer have to create and organize threads yourself; the agent in a space will do it for you.\n\nIt's a new, higher-level way to work with many agents.\n\nAfter using spaces for the past few weeks, we think this might be the future of interacting with agents. There's something special about this way of working. You operate with a birds-eye-view but can still dive into the weeds when necessary. It's more like sitting in the captain's char than down in the trenches.\n\nWe also found that we naturally moved into the space to communicate with each other. Instead of Slack, we found ourselves taking video calls and discussions into the space.\n\nHere are some examples of how we've been using spaces at Amp.\n\n### Collaborate on a New Feature\n\nSpaces were built in a space. Tim, Lewis, Nicolay and the rest of the team shared one called \"Spaces v1\", dropped feedback, bugs and new ideas into the chat, and the agent delegated them into threads. When they needed to talk, they used comments to chat and then tagged in Amp when we were ready.\n\n![The Spaces v1 space: teammates post feedback with replies under each message, the agent notes it and reports that the new Spaces icons shipped, and the side panel lists the space's threads by status.](https://static.ampcode.com/news/spaces-v1-space-light.avif) ![The Spaces v1 space: teammates post feedback with replies under each message, the agent notes it and reports that the new Spaces icons shipped, and the side panel lists the space's threads by status.](https://static.ampcode.com/news/spaces-v1-space-dark.avif)\n\n### Launching and Supporting a Feature\n\nLewis ran the launch of [service accounts](https://ampcode.com/news/service-accounts) from one space. From the space, Lewis could roll out the feature, monitor X, Slack, and bug reports for issues, fix incoming bugs, and send out emails and refunds to affected users. The space monitored user issues and system health for the rest of the week.\n\n![The Service Accounts space: Lewis asks the agent to check for bug reports about service accounts every hour, hands it a bug report to handle, and the agent reports the fix is live, with the space's threads grouped by status in the side panel.](https://static.ampcode.com/news/spaces-service-accounts-light-v2.avif) ![The Service Accounts space: Lewis asks the agent to check for bug reports about service accounts every hour, hands it a bug report to handle, and the agent reports the fix is live, with the space's threads grouped by status in the side panel.](https://static.ampcode.com/news/spaces-service-accounts-dark-v2.avif)\n\n### Regular Security Reviews\n\nWill 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, checked every finding in another, and kept a summary artifact in the space for Will to review and track.\n\n![The Security Review space: Will describes how a daily review should work, the agent runs a design spike and a supervised first run that files 14 issues, and keeps a ledger artifact up to date.](https://static.ampcode.com/news/spaces-security-review-light-v2.avif) ![The Security Review space: Will describes how a daily review should work, the agent runs a design spike and a supervised first run that files 14 issues, and keeps a ledger artifact up to date.](https://static.ampcode.com/news/spaces-security-review-dark-v2.avif)\n\nTo start a space, use the `+` in the `Spaces` section of the sidebar, set a title and a project, and then tell your agent what to work on.\n",
  "authors": [],
  "captured_at": "2026-11-06T18:21:10.909146084+00:00",
  "category": "programming",
  "content_html": "<p>Today we're launching spaces, a new way to interact with agents and your team in Amp.</p>\n<p>A space is a conversation with a single agent whose job is to spawn and coordinate agents for you. You no longer have to create and organize threads yourself; the agent in a space will do it for you.</p>\n<p>It's a new, higher-level way to work with many agents.</p>\n<p>After using spaces for the past few weeks, we think this might be the future of interacting with agents. There's something special about this way of working. You operate with a birds-eye-view but can still dive into the weeds when necessary. It's more like sitting in the captain's char than down in the trenches.</p>\n<p>We also found that we naturally moved into the space to communicate with each other. Instead of Slack, we found ourselves taking video calls and discussions into the space.</p>\n<p>Here are some examples of how we've been using spaces at Amp.</p>\n<h3>Collaborate on a New Feature</h3>\n<p>Spaces were built in a space. Tim, Lewis, Nicolay and the rest of the team shared one called &quot;Spaces v1&quot;, dropped feedback, bugs and new ideas into the chat, and the agent delegated them into threads. When they needed to talk, they used comments to chat and then tagged in Amp when we were ready.</p>\n<p><picture class=\"article-picture article-picture-fallback\" style=\"--image-ratio:16 / 9\"><img src=\"https://static.ampcode.com/news/spaces-v1-space-light.avif\" alt=\"The Spaces v1 space: teammates post feedback with replies under each message, the agent notes it and reports that the new Spaces icons shipped, and the side panel lists the space&#39;s threads by status.\" loading=\"eager\" decoding=\"async\" fetchpriority=\"high\" referrerpolicy=\"no-referrer\" class=\"progressive-image\"></picture> <picture class=\"article-picture article-picture-fallback\" style=\"--image-ratio:16 / 9\"><img src=\"https://static.ampcode.com/news/spaces-v1-space-dark.avif\" alt=\"The Spaces v1 space: teammates post feedback with replies under each message, the agent notes it and reports that the new Spaces icons shipped, and the side panel lists the space&#39;s threads by status.\" loading=\"lazy\" decoding=\"async\" fetchpriority=\"low\" referrerpolicy=\"no-referrer\" class=\"progressive-image\"></picture></p>\n<h3>Launching and Supporting a Feature</h3>\n<p>Lewis ran the launch of <a target=\"_blank\" rel=\"noopener noreferrer\" href=\"https://ampcode.com/news/service-accounts\">service accounts</a> from one space. From the space, Lewis could roll out the feature, monitor X, Slack, and bug reports for issues, fix incoming bugs, and send out emails and refunds to affected users. The space monitored user issues and system health for the rest of the week.</p>\n<p><picture class=\"article-picture article-picture-fallback\" style=\"--image-ratio:16 / 9\"><img src=\"https://static.ampcode.com/news/spaces-service-accounts-light-v2.avif\" alt=\"The Service Accounts space: Lewis asks the agent to check for bug reports about service accounts every hour, hands it a bug report to handle, and the agent reports the fix is live, with the space&#39;s threads grouped by status in the side panel.\" loading=\"lazy\" decoding=\"async\" fetchpriority=\"low\" referrerpolicy=\"no-referrer\" class=\"progressive-image\"></picture> <picture class=\"article-picture article-picture-fallback\" style=\"--image-ratio:16 / 9\"><img src=\"https://static.ampcode.com/news/spaces-service-accounts-dark-v2.avif\" alt=\"The Service Accounts space: Lewis asks the agent to check for bug reports about service accounts every hour, hands it a bug report to handle, and the agent reports the fix is live, with the space&#39;s threads grouped by status in the side panel.\" loading=\"lazy\" decoding=\"async\" fetchpriority=\"low\" referrerpolicy=\"no-referrer\" class=\"progressive-image\"></picture></p>\n<h3>Regular Security Reviews</h3>\n<p>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, checked every finding in another, and kept a summary artifact in the space for Will to review and track.</p>\n<p><picture class=\"article-picture article-picture-fallback\" style=\"--image-ratio:16 / 9\"><img src=\"https://static.ampcode.com/news/spaces-security-review-light-v2.avif\" alt=\"The Security Review space: Will describes how a daily review should work, the agent runs a design spike and a supervised first run that files 14 issues, and keeps a ledger artifact up to date.\" loading=\"lazy\" decoding=\"async\" fetchpriority=\"low\" referrerpolicy=\"no-referrer\" class=\"progressive-image\"></picture> <picture class=\"article-picture article-picture-fallback\" style=\"--image-ratio:16 / 9\"><img src=\"https://static.ampcode.com/news/spaces-security-review-dark-v2.avif\" alt=\"The Security Review space: Will describes how a daily review should work, the agent runs a design spike and a supervised first run that files 14 issues, and keeps a ledger artifact up to date.\" loading=\"lazy\" decoding=\"async\" fetchpriority=\"low\" referrerpolicy=\"no-referrer\" class=\"progressive-image\"></picture></p>\n<p>To start a space, use the <code>+</code> in the <code>Spaces</code> section of the sidebar, set a title and a project, and then tell your agent what to work on.</p>\n",
  "content_markdown": "Today we're launching spaces, a new way to interact with agents and your team in Amp.\n\nA space is a conversation with a single agent whose job is to spawn and coordinate agents for you. You no longer have to create and organize threads yourself; the agent in a space will do it for you.\n\nIt's a new, higher-level way to work with many agents.\n\nAfter using spaces for the past few weeks, we think this might be the future of interacting with agents. There's something special about this way of working. You operate with a birds-eye-view but can still dive into the weeds when necessary. It's more like sitting in the captain's char than down in the trenches.\n\nWe also found that we naturally moved into the space to communicate with each other. Instead of Slack, we found ourselves taking video calls and discussions into the space.\n\nHere are some examples of how we've been using spaces at Amp.\n\n### Collaborate on a New Feature\n\nSpaces were built in a space. Tim, Lewis, Nicolay and the rest of the team shared one called \"Spaces v1\", dropped feedback, bugs and new ideas into the chat, and the agent delegated them into threads. When they needed to talk, they used comments to chat and then tagged in Amp when we were ready.\n\n![The Spaces v1 space: teammates post feedback with replies under each message, the agent notes it and reports that the new Spaces icons shipped, and the side panel lists the space's threads by status.](https://static.ampcode.com/news/spaces-v1-space-light.avif) ![The Spaces v1 space: teammates post feedback with replies under each message, the agent notes it and reports that the new Spaces icons shipped, and the side panel lists the space's threads by status.](https://static.ampcode.com/news/spaces-v1-space-dark.avif)\n\n### Launching and Supporting a Feature\n\nLewis ran the launch of [service accounts](https://ampcode.com/news/service-accounts) from one space. From the space, Lewis could roll out the feature, monitor X, Slack, and bug reports for issues, fix incoming bugs, and send out emails and refunds to affected users. The space monitored user issues and system health for the rest of the week.\n\n![The Service Accounts space: Lewis asks the agent to check for bug reports about service accounts every hour, hands it a bug report to handle, and the agent reports the fix is live, with the space's threads grouped by status in the side panel.](https://static.ampcode.com/news/spaces-service-accounts-light-v2.avif) ![The Service Accounts space: Lewis asks the agent to check for bug reports about service accounts every hour, hands it a bug report to handle, and the agent reports the fix is live, with the space's threads grouped by status in the side panel.](https://static.ampcode.com/news/spaces-service-accounts-dark-v2.avif)\n\n### Regular Security Reviews\n\nWill 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, checked every finding in another, and kept a summary artifact in the space for Will to review and track.\n\n![The Security Review space: Will describes how a daily review should work, the agent runs a design spike and a supervised first run that files 14 issues, and keeps a ledger artifact up to date.](https://static.ampcode.com/news/spaces-security-review-light-v2.avif) ![The Security Review space: Will describes how a daily review should work, the agent runs a design spike and a supervised first run that files 14 issues, and keeps a ledger artifact up to date.](https://static.ampcode.com/news/spaces-security-review-dark-v2.avif)\n\nTo start a space, use the `+` in the `Spaces` section of the sidebar, set a title and a project, and then tell your agent what to work on.\n",
  "dateCreated": "2026-11-06T18:21:10.909146084+00:00",
  "date_created": "2026-11-06T00:00:00+00:00",
  "date_modified": "2026-11-06T00:00:00+00:00",
  "date_published": "2026-11-06T00:00:00+00:00",
  "description": "Today we're launching spaces, a new way to interact with agents and your team in Amp. A space is a conversation with a single agent whose job is to spawn and coordinate agents for you. You no longer have to create and organize threads…",
  "external_url": "https://ampcode.com/news/spaces",
  "git": {
    "commit": "20068632b65d2830a2d54f25ca1d90d697bea2c0",
    "path": "items/ampcode-com/2026/11/2026-11-06-spaces.md",
    "permalink": "https://github.com/aymericbeaumet/aggr-instance/blob/20068632b65d2830a2d54f25ca1d90d697bea2c0/items/ampcode-com/2026/11/2026-11-06-spaces.md"
  },
  "id": "urn:aggr:item:a0d7c8a073704a90dd6aebba6156efed05d7c35b",
  "isBasedOn": {
    "@id": "https://ampcode.com/news/spaces"
  },
  "mainEntity": {
    "@id": "https://ampcode.com/news/spaces",
    "@type": "CreativeWork",
    "archivedAt": {
      "@id": "https://aggr.aymericbeaumet.com/items/ampcode-com/2026-11-06-spaces/#webpage"
    },
    "dateModified": "2026-11-06T00:00:00+00:00",
    "datePublished": "2026-11-06T00:00:00+00:00",
    "headline": "Spaces",
    "image": {
      "@type": "ImageObject",
      "caption": null,
      "height": 90,
      "url": "https://ampcode.com/og?_template=news&_version=7&title=Spaces&date=November+6%2C+2026&tagline=Spaces+are+a+new%2C+higher-level+way+to+work+with+many+agents+and+teammates.&backgroundImage=https%3A%2F%2Fstatic.ampcode.com%2Fnews%2Fspaces-cover.avif&sig=ed2785dd3bf7a53d05a2361d7038665b80cdfaac120bd6ccf6253376c046fd40",
      "width": 160
    },
    "timeRequired": "PT2M",
    "url": "https://ampcode.com/news/spaces",
    "wordCount": 358
  },
  "name": "Archived snapshot: Spaces",
  "preview": {
    "alt": null,
    "color": null,
    "height": 90,
    "placeholder": {
      "data_url": "data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAAEAAAABCAQAAAC1HAwCAAAAC0lEQVR42mNk+A8AAQUBAScY42YAAAAASUVORK5CYII=",
      "hash": ""
    },
    "url": "https://ampcode.com/og?_template=news&_version=7&title=Spaces&date=November+6%2C+2026&tagline=Spaces+are+a+new%2C+higher-level+way+to+work+with+many+agents+and+teammates.&backgroundImage=https%3A%2F%2Fstatic.ampcode.com%2Fnews%2Fspaces-cover.avif&sig=ed2785dd3bf7a53d05a2361d7038665b80cdfaac120bd6ccf6253376c046fd40",
    "width": 160
  },
  "reading_minutes": 2,
  "replicated_at": null,
  "source": "ampcode-com",
  "source_name": "Amp News",
  "summary": "Today we're launching spaces, a new way to interact with agents and your team in Amp. A space is a conversation with a single agent whose job is to spawn and coordinate agents for you. You no longer have to create and organize threads yourself; the agent in a space will do it for you. It's a new, higher-level way to work with many agents. After using spaces for the past few weeks, we think this might be the future of interacting with agents. There's something special about this way of working. You operate with a birds-eye-view but can still dive into the weeds when necessary. It's more like sitting in the captain's char than down in the trenches. We also found that we naturally moved into the space to communicate with each other. Instead of Slack, we found ourselves taking video calls and discussions into the space. Here are some examples of how we've been using spaces at Amp. Collaborate on a New Feature Spaces were built in a space. Tim, Lewis, Nicolay and the rest of the team shared one called \"Spaces v1\", dropped feedback, bugs and new ideas into the chat, and the agent delegated them into threads. When they needed to talk, they used comments to chat and then tagged in Amp when we were ready. Launching and Supporting a Feature Lewis ran the launch of service accounts from one space. From the space, Lewis could roll out the feature, monitor X, Slack, and bug reports for issues, fix incoming bugs, and send out emails and refunds to affected users. The space monitored user issues and system health for the rest of the week. 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, checked every finding in another, and kept a summary artifact in the space for Will to review and track. To start a space, use the + in the Spaces section of the sidebar, set a title and a project, and then tell your agent what to work on.",
  "tags": [],
  "temporalCoverage": "2026-11-06T18:21:10.909146084+00:00",
  "title": "Spaces",
  "url": "https://aggr.aymericbeaumet.com/items/ampcode-com/2026-11-06-spaces/",
  "word_count": 358
}