Find, share, and review artifacts

An artifact is something a session made so you can look at it without reading the whole transcript. It might be a page that explains a design, a screenshot of a change, or a recording of the agent using the app. Artifacts stay after the session ends.

Where artifacts come from

The agent publishes an artifact while it works, and you can ask for one in plain words, such as “publish a page that compares the two options”. The transcript shows a line like Published and the title, and Republished with a version number when the agent updates it. The kinds you’ll meet are:

Sessions also keep run evidence, such as test reports, logs, and coverage. The Evidence chip on the Artifacts page shows it.

When the agent runs an app in its environment, such as a dev server, the transcript shows Opened a preview: and the session’s artifacts list the app with a Live badge. Its title opens the app on a page of its own. Only people who can open the session can see a preview, and it can’t be shared. It ends a few minutes after the run’s environment stops, so ask the agent to start the app again for a new one.

Find an artifact

Open Artifacts from the sidebar to see everything your sessions produced and everything shared with you.

• Whose artifacts narrows the list to Yours and shared with you, From your sessions, Only sessions you own, Shared with you, or Shared with others.
• The chips filter by kind, with Pages, Animations, Screenshots, Recordings, Documents, and Evidence.
• Search titles and sessions finds an artifact by its title or its session.
• Archived shows the archived ones. Choose Restore on one to bring it back.

You can also open an artifact from the session that made it. Its page has Back to session to return there.

Work with an artifact

Each artifact has its own page. The toolbar at the top gives you these controls.

• Version lets you move between versions when the agent has republished it.
• Pin keeps it in the Pinned group at the top of your Artifacts list. You can pin anything you can open, and a pin is yours alone.
• Share controls who can open it.
• The Artifact actions menu has Open in a new tab, which shows it full size, and Download, which saves it. A page offers Download as HTML and Download as Markdown instead.
• If you own the session or collaborate on it, the same menu has Archive, which hides it from the main list for everyone, and Delete…, which removes every version for everyone who could open it. The session’s transcript keeps its line.

An animation has Export instead of a download, for an MP4 video, a Poster image (PNG), or its HTML source. The session’s owner and collaborators can choose Edit to change an animation’s text, timing, and colors, and saving it makes a new version.

On the Artifacts list, Select lets you archive or delete several at once.

Share an artifact

Choose Share on the artifact’s page. Sharing an artifact is acting on the session, so the session’s owner and collaborators can do it.

• Add viewer lets you name people. Viewers can open the artifact even if they can’t open the session.
• Link access is either Restricted, so only people who can open the session and the viewers you add can open it, or Anyone with the link, so anyone who has the link can view every version and its published data, without signing in.
• Copy artifact link copies the address.

A new page or animation starts as Anyone with the link, unless the agent published it restricted, so ask the agent to keep a page restricted when it shows internal data. Screenshots, recordings, and documents start Restricted.

A page the agent publishes from a private session starts Restricted, so only the people who can open the session and the viewers you add can open the page. A page whose link was shared before the session became private stays shared until you change it.

An artifact someone shared with you shows a Shared with you badge. If you open a link to one you can’t see, the page tells you it’s private and suggests asking the owner to share it.

Use a page in another session

Paste a page’s link into a message in another session and the agent there reads it as you. It can read any page you can open yourself, but a page from a private session only if you’re its owner or a collaborator on it or its project, unless the page is shared with Anyone with the link. The agent reads the page’s text and the data it was published with, and it doesn’t refresh a live page’s data.

When the agent can’t read a page, it tells you whose access is missing. Ask the session’s owner to add you, or to share the page. What the agent quotes from a page shows in the session it’s working in, where everyone who can open that session can read it. A session an automation started doesn’t read other sessions’ pages this way.

Send feedback on a page

On a page or an animation, choose Feedback to comment on it directly. Each comment is anchored to the page, so the agent knows exactly what you mean. The button shows how many comments are open.

Pick a tool, then mark the page.

Type what should change and choose Add comment. Each comment gets a numbered badge on the page, and Comments lists them all. You can choose Reply on any comment, and Resolve, Reopen, edit, or Delete on your own. The session’s owner and collaborators can resolve or reopen any comment, and its owner can delete any. Show resolved brings back the ones you’ve closed.

When you’re ready, choose Send all to give every open comment with something new, replies included, to the session as one message. Send on a comment sends just that one. The agent reads them and acts on them. Only the session’s owner and collaborators can send feedback to the agent. Other people who can open the session, and viewers you added, can still leave comments, which the owner can send on. Someone who opened the page only through Anyone with the link doesn’t see its feedback. Each comment records which version it was left on.

In the terminal, evergreen feedback --artifact <id> lists a page’s comments and can send, resolve, reply to, or delete them. You make new highlights and circles on the web, since they need the page on screen.