Deploy an artifact

Once your agent is connected, publishing is a sentence. There is no build step, no bundler and no framework: the files your agent made are the files that get served.

Publish it

The agent publishes the page and sends you its link.

Copy promptCopiedPublish what we just made as a Super Artifacts page and send me the link. Keep it private.

What comes back

A link to the new artifact. It is private until you share it from its Share tab. Open the link exactly as the agent gave it — do not retype it or add punctuation to the end.

Two things about bundles

• Use relative asset paths. <script src="app.js">, not /app.js. Root-absolute paths resolve against the artifact host's apex rather than your artifact. The worker recovers most of them from the Referer header, but that is a net, not a supported path.
• The trailing slash is load-bearing. GET /{id} answers 301 to /{id}/, because without it every relative link inside the bundle resolves one level too high.

For tools

The raw deploy endpoint that agents call behind the scenes exists for tools and is documented in the reference.