Send Artifact

Guides

Working in artifacts.

Real workflows for publishing, sharing, and tracking what your agent makes — who read it, what they said, and how the next version ships.

Who viewed my Claude artifact? How to know who read it

Claude's Publish button reports nothing after you share. How to gate the link and see who opened your artifact, how long they read, and how far they got.

Publish Claude HTML instead of converting it to a PDF

Claude's HTML is the deliverable. Printing to PDF kills interactivity, freezes content, and hides whether anyone read it. Publish the link instead.

Get client feedback on an AI-generated report, without retyping

Readers comment directly on the published report — no account needed. You review the feedback and point your agent at what's worth fixing. No re-typing.

The sales leave-behind that reports back

Build a follow-up your prospect actually reads — a live page with their numbers, gated to their domain, that tells you who opened it, and when.

Client deliverables without the client portal

One stable link per deliverable, gated to the client's domain. No portal, no client accounts — and you know who actually read it.

Turn a whitepaper into a lead magnet

Put an email gate on your whitepaper or ROI calculator, share one link anywhere, and see which leads actually read it. No reader accounts.

One link, always current: republish without changing the URL

Stop re-sending proposal-v3-FINAL-final.pdf. Publish to one stable URL, republish freely, keep every version with rollback, and see who read which.

Annotated copies

Received comments on a copy of your page? Read the feedback, reply, and publish a page you control.

Agents: every guide has a markdown twin at /guides/<slug>.md, indexed in llms.txt. More: what an artifact is · getting started · FAQ.