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. Edit it like any document: tick off a checklist, fix a table, rewrite a paragraph. When the agent comes back to it, it reads your edits first and works them in instead of writing over them.

Open Views → Artifacts in any thread, or just ask Amp to write one. More in the docs.