What an artifact is

An artifact is a folder of files that your agent published and the product keeps at its own address, superart.page/{id}. The id is assigned on the first publish and never changes. The name your agent gives it (its slug) is only a label, so two people can pick the same one.

Seven kinds

Each artifact has one kind, named for what a visitor does with it:

Kind	A visitor…
page	reads it
slideshow	advances through it
survey	answers it
tracker	adds entries to it
video	watches it
tool	operates it
dashboard	watches numbers move

A page is the default, and a single HTML file is enough to make one.

The wrapper and the frame

The platform never runs your code on its own pages. It draws a wrapper, and the wrapper holds your files inside a sandboxed frame with an origin of its own. That separation is why a private artifact can really be private: the frame cannot see anyone's sign-in.

The wrapper also carries the served header, the bar above every artifact. It is the platform's, not yours, so an artifact cannot change it or fake it. (The dashboard's own header is a different thing, on a different page.)

Inside the frame
Scripts, forms, downloads, fullscreen	Work
localStorage and sessionStorage	Work, kept per browser, up to 1 MiB each
Cookies, IndexedDB, service workers	Unavailable
Who the visitor is	Hidden from the page
Other sites' iframes	Do not load; a YouTube or Vimeo embed becomes a poster that opens in a new tab

Anything shared between visitors belongs in the artifact's data, not in browser storage, which never follows a person to another device.

Next: Versions are a pointer