Getting started · about two minutes

Publish your first artifact.

Your agent does the setup itself — you confirm your email once. Here is the whole flow, from a prototype in your chat to a live, access-controlled link.

1. 01
   Point your agent at the site
   With your artifact open in your coding agent, say:Publish this to sendartifact.comThe agent reads the site's own instructions and takes it from there — nothing to install first.
2. 02
   Confirm your email
   The agent asks for your email and suggests a handle — your permanent public prefix, as in sendartifact.com/you. A 6-digit code lands in your inbox; paste it back. That is the entire sign-up: no password, no form, and the key your agent receives is stored only as a hash.
3. 03
   Share it
   Your artifact goes live at a stable URL, private by default — nobody else can open it until you say so:Share it by link · Invite jane@acme.com · Invite everyone at acme.comRepublishing keeps the same URL and adds a new version, so a shared link never goes stale.

Have an HTML file from a chat?

Download the .html file your chat created. Choose Upload an HTML file, sign in, and pick the file. Choose who can open it before publishing. To update it later, upload the revised file with the same link name.

The feedback loop

This is the part that changes how reviews work. Anyone who can open your artifact can select the text they mean, or choose Drop a pin to pin a spot — in a meeting or async, no account needed. Afterward, back in your agent:

The agent pulls the comments, sees exactly which element each one points at, makes the edits, republishes to the same URL, and replies to every thread with what changed. Feedback in, new version out — no copy-pasting screenshots into chat.

Handy asks, once you're set up

• “Who's viewed my artifact?” — view counts and viewers; on email-gated links, verified addresses are flagged as proven.
• “Make it require a verified email” — readers prove who they are with a one-time code or Google before the page renders.
• “Turn off comments on this one” — for collateral where readers are an audience, not reviewers.

Where to go next: guides to real workflows — who read it, client feedback, lead capture · wondering about your data? the security overview · questions: support@sendartifact.com.