Open immediately
Public access opens directly for anyone who has the URL.
AI-GENERATED REPORTS · CLIENT-READY DELIVERY
Need to explain research, project progress, or spreadsheet results? Your AI agent can turn your source material into a visual HTML report: conclusions first, evidence beside each claim, detail when it matters. Start with a draft, not connection setup. Review it, then approve publishing through share/artifacts and choose who can open the link.
THE SHORT ANSWER · 01
An HTML-native AI report is a responsive browser document that uses real HTML text, typography, layout, and CSS-built visuals to lead a reader from context and evidence to a recommendation. It is a static report, not a live dashboard or web app.
FIRST-PARTY EVIDENCE · 02
Your client opens a polished report in the browser, follows the argument from evidence to recommendation, and can return to the same link after every revision.
365 days of questionable judgment
The groupA REVIEWABLE WORKFLOW · 03
Keep the analysis and revisions in your agent conversation. share/artifacts handles the published page and access; you check the evidence and decide what is ready for the audience.
Name the audience, intended decision, publishing permission, and validated source material.
Give your agent the source material, or use authorized context it already has. Ask for one central finding, evidence, recommendation, and method. Review the local draft before approving publication.
After checking figures, sources, caveats, sensitive or private information, and permission to publish, connect a compatible agent and approve publishing. Inspect the owner-only result and narrow-screen rendering.
Keep the report owner-only, make it public, or restrict it by password, exact email addresses, or exact email domain; optionally set expiration.
A USEFUL STARTING PROMPT
Ask for the decision, not a pile of charts.Turn my notes or analysis into a responsive visual report for [audience]. Use authorized context or ask for missing sources. Lead with the decision, preserve exact figures and sources, separate facts from inference, and make caveats visible. Retrieve my saved style if available. Let me review the draft before publishing, and ask for explicit approval before publishing or changing access.
share/artifacts sanitizes the report's delivery behavior. It does not fact-check the report or authorize its contents; confirm accuracy, confidentiality, and permission to publish before sharing it.
THE HANDOFF · 04
Updating the existing artifact replaces its HTML while preserving its canonical share URL. Reviewers and recipients keep one address; you decide when its access changes.
Public access opens directly for anyone who has the URL.
Password access asks the recipient for the password you set.
Exact-email and email-domain access require a verified matching account.
Restricted methods work as alternatives. Expiration ends recipient access at the time you choose.
CHOOSE FOR THE RECIPIENT · 05
A browser link is excellent for communicating a current conclusion. It is not the right replacement for every working file.
Best for responsive reading, visual narrative, and one current share URL.
Better for fixed pagination, printing, formal filing, or offline archival.
Better when recipients need raw cells, formulas, sorting, or their own analysis.
Better when the handoff requires collaborative rewriting or tracked edits.
Choose HTML when the job is to understand and act on the report; choose a file when the recipient needs to edit, calculate, print, or archive it.
SAFE STATIC MODE · 06
Sanitization removes scripts, forms, embeds, event handlers, and refresh redirects. CSP blocks active API connections. Publisher-selected HTTPS images and fonts may still load from their hosts.
That boundary keeps the published result static: it can communicate data beautifully, but it does not stay connected to a live source.
THE REPORT IS READY WHEN THE DECISION IS CLEAR