From a Claude artifact to a vibe-coded app to a multi-file Codex bundle — how to share what an AI tool builds, as a private link, without a deploy pipeline.
The moment is always the same: you built something with an AI tool, it works in the preview, and someone who isn't sitting next to you needs to see it. The tooling that was so good at building goes quiet at sharing — and the two endpoints people reach for (a screenshot, a full deploy) are usually too little or too much.
Here's the whole spectrum, and where each piece goes deep.
The cleanest export is one self-contained .html with everything inlined. How to privately share a Claude or ChatGPT artifact covers the handoff to one client — drop the file, get a link, no chat history attached.
Mid-build, each round produces a new version, and the reviewer needs that version, not the chat that made it. AI builders: sharing mid-prompt prototypes during iteration covers per-round short-expiry links that self-retire after each pass.
A vibe-coded app from Bolt, v0, Lovable, or Cursor lives in an in-between state — past idea, not yet product. Sharing a vibe-coded app as a private link covers the review-it-before-you-deploy shape for a self-contained front end.
Some tools export a folder, not a file. Sharing a multi-file AI app as one private link covers zipping the project so the host serves the whole thing — index.html plus its CSS, JS, and assets — with the relative paths intact.
Not everything should stay private. AI product landings: from prompt-built page to public URL covers the finished, public case — when the page should be indexed and found.
The dividing line is the backend. A self-contained front end — HTML, CSS, JS, assets that run in the visitor's browser — is a file, and a file shares as a link. The moment the app needs server-side execution (a database, auth, API routes), it's not a file anymore and needs a real deploy. The private link covers the step before that, and every case that never needs a backend at all.
See the full set in the Sharing AI-built apps archive.
A disabled Publish button isn't one bug — it's four different situations wearing the same grey. Two of them are permanent, two clear in a minute. Here's how to tell which one you're looking at, and how to get the page to the person waiting for it either way.
The message is about Anthropic's side, not yours, and it usually clears on its own. The risk isn't the outage — it's what people press while waiting. Here's the safe order of operations, and how to get the work out of the artifact while you wait.
You built something in Claude, came back weeks later, and it's gone. Usually it isn't deleted — it's sitting inside a conversation you can no longer find. Here's how to get it back, and the one case where it really is unrecoverable.
miinideck turns a single HTML file into an unguessable link with optional password and expiry. Default-private, never indexed.