Share an AI-made HTML artifact with your team
Assistants are good at producing small interactive pages: a dashboard mock, a pricing calculator, a one-page explainer. Getting colleagues to see it working is the awkward part. This guide covers sharing that kind of single-file HTML "artifact" as a live link your team can comment on.
What works
Ollav hosts one self-contained HTML file up to 15 MB. Most assistant-made artifacts already fit:
- Inline
<style>and<script>: fine. - Libraries from a CDN (
https://cdn.jsdelivr.net/...): fine. - Calls to public, CORS-friendly APIs: fine.
- Images as
data:URIs or absolute URLs: fine. - Relative files (
./data.json,img/logo.png): won't load. Ask the assistant to inline them. - Server code (API routes, databases): not supported. It's static hosting.
If the artifact is React or TSX source rather than HTML, ask the assistant: "Give me this as a single self-contained HTML file that loads React from a CDN."
Three ways to share it
From the browser
- Save the HTML to a file (or copy it).
- Open https://app.ollav.app and drop the file, or paste the HTML.
- Copy the link and send it to your team.
From an agent with MCP
Connect Ollav once (setup for each client), then just ask:
Share this page on Ollav and give me the link.The agent calls share_html and replies with the URL.
From a terminal
curl -F "file=@artifact.html" -H "Authorization: Bearer $OLLAV_API_KEY" -H "X-Ollav-Client: agent" https://app.ollav.app/api/documentsWho can see it
| Visibility | Who can open the link | Who can comment |
|---|---|---|
workspace (default) | Members of your workspace | Members |
link | Anyone signed in to Ollav with the URL | Members |
public | Anyone with the URL, no sign-in | Members |
To bring in one outside reviewer without opening the whole workspace, share that document with their email. They become a guest of just that document.
Updating it
When you change the artifact, publish it as a new version of the same document rather than uploading it again. The link stays the same and the comments carry over. In the browser, re-upload with the same filename. An agent calls publish_new_version with the document's slug.