Sharing what Claude Code built: a link, not a zip

Claude Code leaves you with files in a folder. The person you're building for needs a link that renders, stays current, and maybe stays private. Your options:

For a one-off file: paste hosts

If it's a single HTML file you'll never touch again, a paste-and-share artifact host is the lightest path: drag, get a link, done. The trouble starts when the thing keeps changing: each update mints a new link, and "which one is current?" becomes your job.

For technical audiences: GitHub Pages

Free, reliable, and the strongest version history anywhere, if everyone involved is comfortable with git. For nontechnical reviewers, "just look at the branch" ends the conversation, and the initial Pages setup is a hurdle someone technical has to clear.

For projects that keep evolving: a project home

Plyo is built for exactly this shape of problem. Claude Code connects with one paste (setup here), and then:

• One stable URL: publish gives a permanent address; updates republish to it, rollback is instant.
• Private links: every draft gets its own preview URL, optionally password-protected.
• Whole-folder fidelity: Claude pushes the entire project, so images and assets arrive intact instead of 404ing.
• Review without accounts: reviewers open the link and pin comments right on the page; you copy any comment out as a ready-made prompt for Claude to act on. Nobody involved touches git.
• Version history: every save is a restorable checkpoint with a plain-English note.

The rule of thumb

Throwaway file → paste host. Technical team already on GitHub → Pages. A living project that nontechnical people need to see and react to → give it a home. If you're reading this page, you're probably in the third case.