Amp 2026-11-08 build: Spaces, Artifacts, and GitLab#
Published by Alex Sorokoletov
Part of the Amp Version Tracker series. | ampcode.com | News
Amp build 0.0.1794139239, one week on from 0.0.1793534443, adds Spaces, where one agent creates and coordinates other agents; Artifacts, documents a thread's agent and teammates edit together; service accounts that own threads for the whole workspace; a GitLab integration; and a website feedback widget that opens a thread. These shipped between November 2 and November 6, 2026.[1][2][3][4][5]
What shipped this week#
| Change | What You Get |
|---|---|
| Spaces | A conversation with an agent that creates and coordinates other agents and organizes their threads for you (Nov 6).[5] |
| Artifacts | Documents attached to one thread that you, your teammates, and the agent all edit (Nov 2).[1] |
| Service accounts | Workspace-owned accounts whose threads every member can view and steer (Nov 3).[2] |
| GitLab integration | Connect gitlab.com or a self-managed instance; agents clone, push, open merge requests, and read issues and pipelines (Nov 5).[3] |
| Close the Loop | A feedback widget on your site that turns a click and a note into a thread in your project (Nov 6).[4] |
Spaces#
A space is a single conversation with an agent whose job is to create and coordinate other agents.[5] You describe the work, and that agent sets up and organizes the threads for you. You keep a high-level view and can open any thread for detail.[5] A space can run recurring tasks: one example checks for service-account bug reports every hour. It can also hold a summary document the team tracks.[5] The announcement's security-review example set a goal, split the codebase into 16 areas, reviewed each in its own thread, checked findings in a separate thread, and filed 14 issues.[5] You start one from the + in the Spaces section of the sidebar, set a title and project, and tell the agent what to work on.[5]
Artifacts#
Artifacts are documents attached to a single thread that the agent, you, and your teammates edit.[1] When the agent has something to read, such as a plan, report, or call notes, it writes an artifact, and you can also ask it for one.[1] The artifact opens next to the thread and you edit it like any document, ticking off a checklist or rewriting a paragraph. When the agent returns to it, it reads your edits first and works them in.[1] One example compares two Markdown-preview builds side by side with their files, checks, and costs; another charts model calls falling from 3.9k to 978 for a proposed change.[1] Open them from Views → Artifacts in any thread.[1]
Service accounts#
A service account is a workspace-owned account, created by an admin, with its own API keys and third-party credentials.[2] Threads started under it can be viewed by every workspace member, and any member can send messages in them and steer the work.[2] Because that access is shared, the docs warn to give a service account only credentials you would hand to all members.[2] A CI job can start a thread with amp -ox when a build fails; setting AMP_API_KEY to the service account's key makes that thread belong to the account.[2]
GitLab integration#
The GitLab integration connects a gitlab.com account or a self-managed instance, letting you start projects from your GitLab repositories.[3] Orbs clone and push as you and come with glab signed in. The agent opens merge requests, comments on them, and reads issues and pipelines; for an MR it opens, it can subscribe to comments and CI results, and reviewer requests and failed pipelines appear in the thread that wrote the code.[3] A spawner can start a new orb for every new MR or issue, each with its own thread, and a workspace admin can run a spawner as a service account.[3] Each person connects GitLab under Settings → Integrations & MCP, and a group owner installs Push Updates once for the workspace.[3]
Close the Loop#
Close the Loop sends feedback to Amp from your own website.[4] You enable the feedback widget in your project settings and add one script to the site. Open the site with ?amp in the URL, click any element, write what you want changed, and send; Amp starts a new thread in your project with your comments, and you ship the change from there.[4] After the first use the widget stays visible on the site until you hide it.[4]
Threads shared across a team and its agents#
This week's changes widen who and what a thread involves. A space makes one person the overseer of many agents; artifacts give a thread a document everyone edits in place; service accounts put a thread's ownership on the workspace; and GitLab spawners open threads from repository events.
Put together, they let an automation run under a workspace identity. A PR listener, an hourly bug-report scan, or a CI job that calls amp -ox can run from a service account and keep going when the person who set it up is away.[2] The thread stays the single place the work happens, while who owns it and how many agents touch it both grow.
Sources#
- Amp News: "Artifacts," November 2, 2026.
- Amp News: "Service Accounts," November 3, 2026.
- Amp News: "GitLab Integration," November 5, 2026.
- Amp News: "Close the Loop," November 6, 2026.
- Amp News: "Spaces," November 6, 2026.
Previous Amp analysis: Amp 2026-11-01 (November 1, 2026)
All 8 Amp analyses: Amp Version Tracker · Official Amp changelog