Share a Claude Code artifact for review

By Angle Labs GmbH. Claude Code facts read on 22 October 2026.

The short answer

For a quick look, Claude Code's own Share control is enough: a public link opens for anyone, with no claude.ai sign-in. According to Claude Code's docs, though, people who reach the page only through that public link do not see its comments and cannot add any. If you want a client or reviewer outside your organization to comment, or you want to limit the page to named email addresses, publish the same page's HTML to Artifact Publisher and send that link. Claude Code then reads the comments back over MCP.

What Claude Code's own sharing does

From the Claude Code docs page "Share session output as artifacts" (code.claude.com; shown as text because this site links to no third-party pages), read on 22 October 2026:

• Artifacts need a paid Claude plan and a Claude Code session signed in to claude.ai with /login. In the docs' words, "Sessions using an API key, gateway token, or cloud-provider credential cannot publish." Artifacts are also off by default when you run Claude Code with -p from your own terminal or scripts.
• A new artifact is private to you. You share it from the Share control in the page header.
• A public link opens for anyone on the internet, with no claude.ai sign-in. In an organization, public sharing stays off until an Owner turns it on.
• Sharing with named people inside your organization, and the comments that come with it, is on Claude plans for organizations; on an individual plan an artifact is private or public. Comments are for those people. Viewers whose only access is the public link do not see the comments and cannot add any.
• Each publish becomes a version, and the page updates in place for anyone who has it open. You can delete an artifact from /artifacts, and its link stops working.
• The page can load scripts from a few public CDNs and fonts from Google Fonts, and the rendered page can be up to 16 MiB.

Plans and sharing settings change, so check that page for your account before you rely on any of this.

Which one fits

If your reviewers are all in your claude.ai organization and your plan includes organization sharing, Claude Code's own comments may be all you need.

1. Connect Artifact Publisher to Claude Code

Create a workspace in your account, copy the publisher key (it is shown once) and add the MCP server with one command. Publish HTML from Claude Code walks through each step and what Claude Code prints. Free plan available.

2. Publish the page as a review link

In the session that made the artifact, ask Claude Code to save it as one HTML file and publish it. The page runs in a sandbox with no network access, so the prompt asks for everything inline:

Save the page you just made as one self-contained HTML file, with all CSS, scripts, images and data inline and nothing loaded from other sites. Then publish that HTML with the artifact-publisher MCP server as a public artifact titled "Pricing page draft", and reply with the share link and the artifact_id.

Claude Code calls publish_artifact with a title and the html. The result has the link, in the form https://app.artifactpublisher.com/artifact/<slug>. Open it in a private window before you send it: a page that relied on a CDN library or a claude.ai connector will show the gaps there. The document can be up to 10 MiB of UTF-8 (25 MiB on the Max plan).

3. Send the link and collect comments

On a public link, the reviewer opens the page in any browser, opens the comments from the bubble on the page and leaves a comment. No account needed to comment on a public link, and the name field is optional. Each comment is pinned to the version the reviewer was looking at.

Back in Claude Code, one prompt turns the comments into a new version:

Read the open comments on artifact <artifact_id> with the artifact-publisher MCP server, make the changes they ask for, publish the result as a new version of the same artifact, and reply to each comment with what you changed.

Claude Code reads the comments with get_feedback, publishes the change withupdate_artifact (a new version behind the same link, so the reviewer keeps the link they have) and answers with reply_to_feedback. Each comment takes one reply. There are no webhooks: Claude Code reads the comments when you ask it to.

4. Restrict it or take it back

A public link is not authenticated: anyone it is forwarded to can open it and comment. To limit the page to named people, switch it to allowlist with set_artifact_access. The reviewer then signs in with an Artifact Publisher account whose primary email is on the list:

{ "artifact_id": "<artifact_id>", "visibility": "allowlist", "allowed_emails": ["reviewer@example.com"] }

private limits it to you. When the review is done, revoke_artifact stops serving the page. It cannot recall a copy someone already saved.

Limits to know

• One self-contained HTML document per version. Artifact Publisher is not a general web host.
• The page has no network access: CDN scripts, web fonts, remote images and API calls do not load. Links a reader clicks still open, in a new tab.
• Artifact Publisher does not read your Claude account and does not copy artifacts out of claude.ai. Claude Code sends the HTML when you ask it to.
• The publisher needs an account; the reader of a public link does not.

Next

• Publish HTML from Claude Code, step by step
• Share a Claude artifact without a Claude account, for artifacts made in Claude chats
• Publish HTML from Codex, step by step
• Publish HTML over MCP from Cursor, VS Code and other clients
• Host an HTML file and share a link: the common ways, side by side
• All guides
• Quickstart, MCP integration, FAQ and privacy