group-chat-report.html
Download it. Find it. Open it. Wonder if it is the latest version.
THE FILE HANDOFFSHARE HTML ONLINE
Turn your HTML file into a shareable link.
Give your HTML to your connected AI agent. share/artifacts hosts the page, gives you a link, and lets you control who can open it—without Git or deployment setup.
No HTML file yet? Create an artifact with your agent.
HAVE THE FILE? START HERE.
Your file. Your agent. One request.
Attach your HTML file to your connected agent and ask:
“Prepare this complete HTML for static sharing. Check local files and unsupported features. Show me a preview and wait for my approval. Then publish through share/artifacts, keep it owner-only, and return the link.”
Connect through MCP first. You review and approve before anything is published.
Decisions. Owners.
What happens next.
Open a meeting decision record and its source notes.
THE SHORT ANSWER
How do you share an HTML page online?
Connect a compatible AI agent to share/artifacts through MCP, provide your complete HTML file, and approve publishing. share/artifacts hosts the supported static page and returns a URL. New pages are owner-only; choose access before sending the link to your audience.
A LINK, NOT AN ATTACHMENT
Send the page.
Not the file.
Give people a page they can open in their browser. See what a published HTML report looks like.
FROM FINISHED HTML TO A LIVE URL
Ask. Review. Share.
- 01
Connect your agent
Sign in or create a share/artifacts account, then authorize a compatible MCP agent.
- 02
Prepare your file
Provide the complete HTML. Ask your agent to check local assets and unsupported features.
- 03
Review and publish
Review the draft, then ask your agent to publish. Open the returned link to check the hosted page.
- 04
Choose access. Share.
Keep it private, make it public, or restrict access—then send the URL.
WHY THE URL MATTERS
Hosting, access, and updates. Handled.
No hosting setup
share/artifacts serves your static HTML. No repository, deployment pipeline, or separate hosting account.
Update the page. Keep the link.
Give your agent the existing link and complete replacement HTML. Your readers keep the same address.
You choose access
Share publicly or limit who can open the artifact. Choose private sharing for your audience.
SAFE STATIC PUBLISHING
For documents.
Not live apps.
Reports, presentations, briefs, and explainers work as static HTML. Include your CSS in the file and replace local asset paths. JavaScript, forms, embeds, and live API calls are not supported.
HTTPS images and fonts can still load from other hosts, including CSS background images. Links can lead to other sites. Check the facts, private details, and destinations before sharing. See what these protections do—and do not—cover.
- Scripts stay offJavaScript from the submitted HTML cannot run.
- Forms stay offEmbedded forms and form submissions are disabled.
- Your app stays separatePublished content lives away from the trusted product.
QUESTIONS, ANSWERED
Sharing HTML FAQ.
How do I share an HTML page online?
Give the complete HTML file to a compatible connected AI agent, review the page, and ask the agent to publish it through share/artifacts. Open the returned URL, choose who can access it, and send the link instead of the file. This is an agent publishing workflow, not a drag-and-drop file host.
Will local images, scripts, and styles work after publishing?
Not automatically. Include the page’s CSS in the HTML and replace local image or font references with supported HTTPS or embedded data URLs. JavaScript, forms, and embeds are removed. Ask your agent to check the complete HTML for these dependencies, then review the published result before sharing it.
Do I need Git, a repository, or a deployment account?
No. Connect a compatible agent, review your artifact, and ask it to publish. Choose access and share the returned URL. The publishing workflow does not require a repository or deployment setup.
Can my AI agent publish HTML for me?
Yes. Connect a compatible agent through MCP and approve its permissions. Review the draft, then ask it to publish the HTML artifact. The agent receives the finished share URL and can give it back to you in the conversation.
Can I update the page without changing its link?
Yes. Ask a compatible connected agent to update the existing artifact with the complete replacement HTML. The artifact keeps its page ID and share URL, so recipients can keep the link they already have.
Is shared HTML safe to open?
share/artifacts sanitizes published HTML, disables scripts, forms, and external API calls, adds a strict browser security policy, and serves the page from a separate content origin. HTTPS images and fonts can still load from other hosts, and ordinary links can lead elsewhere. Review the content and links; these protections do not verify claims or make every page trustworthy.
Who can open a newly published artifact?
A newly published artifact is private to its owner until access is chosen. You can make it public or limit access with a password, exact recipients, your organization, or an expiration time.
HAVE YOUR HTML READY?