Share the result, not the conversation.
We publish only the HTML your agent submits. Check that it contains the information you intend to share.
AI ARTIFACTS / MADE TO LEAVE THE CHAT
Your best AI work deserves more than a screenshot.
Use your connected agent to turn ideas, notes, and analysis into a designed HTML page. Review it, publish with share/artifacts, and send a link your audience can open in a browser.
Already have the HTML? Turn your file into a link.
“Turn these options into a page that helps my client decide.”
The recommendation, tradeoffs, and decision—all in one place.
Open the complete decision brief01 / BEYOND THE REPLY
An AI artifact is a standalone output from a conversation: a brief to send, a checklist to follow, or an explanation to return to. The conversation helps you create it. The artifact gives someone else the useful result.
Here, that result is a static HTML page—not a chat transcript, model file, or running app. Reports and presentations are two possibilities, not the limit of the format.
02 / GIVE THE WORK ITS OWN SHAPE
Your agent can design around what the reader needs to understand. Open these worked examples to inspect the full HTML result, the source material, and a request you can adapt.
Separate what was decided from what still needs an owner or an answer.
Open the decision record ↗FROM DENSE INFORMATIONUse hierarchy, space, and emphasis to make the important information easier to see.
Open the information design example ↗Explore more AI-made HTML examples · Give your artifacts a reusable style
03 / KEEP CREATING WHERE THE CONTEXT IS
Your agent creates and revises the HTML. share/artifacts hosts the approved page and controls who can open it.
Tell your agent who will read it, what they need to understand, and which notes it may use. Ask for a complete static HTML page.
Check the facts, layout, links, and private details. Ask for changes before you approve publishing.
Connect a compatible agent through MCP and ask it to publish. Open the returned URL, check the hosted result, and choose the audience before sending it.
START WITH THIS REQUEST
“Turn the notes above into a self-contained HTML artifact for [audience]. Help them understand [key question] and [next action]. Keep the facts and uncertainties clear. Use a readable layout with no scripts or forms. Show me the draft before publishing.”
Replace the brackets with your own context. Follow the full agent-publishing guide.
04 / KNOW WHAT YOU’RE SHARING
HTML artifact hosting gives the work a browser address. It does not make every AI-generated application compatible—or every AI-generated claim correct.
We publish only the HTML your agent submits. Check that it contains the information you intend to share.
Publish owner-only for review or explicitly choose another access mode. Learn how private sharing works.
Update the same artifact with revised HTML. Readers can reopen or refresh to see it. See the update workflow.
Scripts, forms, and API calls are disabled. External images and fonts may still load. Understand the protections and limits.
QUESTIONS BEFORE YOU SHARE
In an AI conversation, an artifact is a standalone piece of work the AI creates, such as a brief, diagram, checklist, or HTML page. Unlike a chat reply, it is designed to be used outside the conversation. Here, we focus on artifacts made as static HTML pages.
For an HTML artifact, connect a compatible AI agent to share/artifacts, review the finished HTML, and ask the agent to publish it. Open the returned link to check the result, choose who can access it, and send the URL. If your output is another file type, ask your agent to create a static HTML version and review it first.
No. share/artifacts publishes only the HTML your agent submits, not your conversation history. The agent may include information from your conversation in that HTML, so check the draft for private details before publishing.
Yes. A new publication is owner-only unless you explicitly choose another access mode. You can use a password, verified email recipients, or an organization email-domain rule, and set an expiration. Requirements for readers depend on the access mode. An unguessable link or noindex instruction is not a substitute for access control.
Yes. Give your connected agent the existing page ID or share URL and the complete revised HTML. Ask it to update that artifact, not create a new one. The share URL stays the same; readers see the latest successful update when they reopen or refresh the page. Existing access and expiration still apply.
No. share/artifacts hosts static HTML artifacts, not interactive apps or arbitrary files. Scripts, forms, embeds, and external API calls are disabled. Text, CSS layouts, and supported visuals can remain; external images and fonts may still load from their hosts. Review the published result and its links before sharing.
FROM USEFUL CONVERSATION TO USEFUL OUTPUT