# Amp — Artifacts

- Company: Amp (ampcode.com)
- Announced: 2026-11-02
- Category: capability-change
- Coverage: not counted
- Announcement: yes
- Group: announcements
- Source: https://ampcode.com/news/artifacts
- Record: https://forck.live/items/30877-artifacts
- Subject: Amp

Amp is letting agents collaborate with users and teammates inside Artifacts, documents that belong to a single thread and that the agent, the user and teammates can all edit. The agent writes an artifact on its own when it has something to read, such as a plan, a report or notes from a call, instead of posting a long reply, and the artifact opens next to the thread. Users edit artifacts like any document, ticking off a checklist, fixing a table or rewriting a paragraph, and when the agent returns to the artifact it reads those edits first and works them in rather than writing over them. Artifacts also collect findings across threads: one example gathered what the agent found after going through 60 threads on the cost of waiting on long shell commands, and another put two competing implementations side by side with what each costs and which to ship first. Artifacts are reached through Views → Artifacts in any thread, or by asking Amp to write one.

## Evidence

Verbatim from https://ampcode.com/news/artifacts:

> Agents in Amp can now collaborate with you in Artifacts. These are documents that belong to a single thread and that the agent, you, and your teammates can all edit.
> 
> Here are two examples from our real threads.
> 
> This one is from Nicolay's thread, where he asked whether Amp wastes model calls while it waits on a long shell command. The agent went through 60 of our threads and wrote up what it found: how much the waiting costs, why, and a plan to fix it in two steps. Reading it gets you up to speed on the problem before you decide what to build:
> 
> Artifacts also work well for pulling together what several threads found. In Beyang's thread, a user had asked for a rendered preview of Markdown files in the Changes pane. Beyang had the agent build two versions at once, each in its own orb. When both reported back, the agent put them side by side in one artifact, with what each costs and which one to ship first:
> 
> You don't have to ask for one. When the agent has something for you to read, like a plan, a report, or notes from a call, it writes an artifact instead of a long reply. The artifact opens next to the thread.

---

Record: https://forck.live/items/30877-artifacts
Catalogue: https://forck.live/llms.txt
Current issue: https://forck.live/feed.md