Claude writes a local HTML file and gives no link?

Artifacts aren't on for this session. Check that you signed in with /login, not an API key. On Team or Enterprise, ask an Owner whether artifacts are turned on.

The publish fails because the page is too big?

A page must be 16 MiB or smaller, and embedded images are the usual cause. Ask Claude to draw diagrams in SVG or HTML instead.

A teammate can't open the link?

They need to sign in to claude.ai as a member of your organization. On Team and Enterprise, public links stay off until an Owner turns on External sharing.

A new session made a second page instead?

Without the link, a new session starts a new artifact. Give Claude the link, or attach the page from /artifacts, then ask again.

Claude says it can't read comments?

Comments need Claude Code 2.1.221 or later. Run claude update, start a new session and ask again.

Claude CodeTutorials Open Claude Code

Share a live session page with Claude Code Artifacts

Turn a Claude Code session into a live artifact page, share it with your team and update it at the same link, in about 15 minutes.

By Recaply EditorsIntermediate15 min5 stepsUpdated Nov 10, 2026

A blank sheet on a small easel, one hand drawing on it with a pencil while another hand points at it

What you need

A paid Claude planPro is $20 a month and includes Claude Code. Sharing with named teammates needs Team, from $25 a seat a month.
Claude Code, signed in with your Claude accountSessions that run on an API key, or on a cloud provider such as Amazon Bedrock, can't publish artifacts.
A session with work to showSuch as a pull request, test results or data the session has already pulled.

Artifacts are off for organizations that use customer-managed keys, HIPAA or Zero Data Retention.

Step 1: Check that your session can publish
2 min
Artifacts need a claude.ai login. Without one, Claude saves a local file instead of a page.
1. In Claude Code, run /login and sign in with your Claude account.
2. Run /config and check that the Artifacts row is turned on.
You should see the Artifacts row turned on in /config.
Claude writes a local HTML file and gives no link?
Artifacts aren't on for this session. Check that you signed in with /login, not an API key. On Team or Enterprise, ask an Owner whether artifacts are turned on.
Step 2: Ask for an artifact
4 min
A page beats terminal text for diffs, charts and options you want to compare side by side.
1. Do your task as usual, such as a review of an open pull request.
2. Ask for a page and say what it should show. Try the prompt below.
3. If Claude Code asks before it publishes, say yes. It asks in plan mode, for example.
Your prompt
```
Make an artifact that walks through this PR. Render the diff with notes in the margin, and color-code the findings by severity.
```
You should see a claude.ai link in the terminal, and the new page open in your browser.
The publish fails because the page is too big?
A page must be 16 MiB or smaller, and embedded images are the usual cause. Ask Claude to draw diagrams in SVG or HTML instead.
Claude saves the page in a temporary folder outside your project, unless you name a place. Press Ctrl+] to reopen the latest artifact.
Step 3: Share it with your team
2 min
A new artifact is private to you until you share it.
1. On the page, open Share in the header.
2. On Team or Enterprise, add teammates by name, or pick everyone in your organization.
3. Turn on Always share latest version, then click Copy link and send it.
You should see the people you added in the share menu, and a link ready to paste.
A teammate can't open the link?
They need to sign in to claude.ai as a member of your organization. On Team and Enterprise, public links stay off until an Owner turns on External sharing.
On Pro, Max and Ultra, you share a public link that anyone can open without signing in.
Step 4: Update the page as you work
3 min
Every publish goes to the same link, so reviewers never need a new one.
1. Ask Claude to change the page and publish it again. Try the prompt below.
2. Watch the open page update in place.
3. To update it from a new session, run /artifacts and attach it, or paste its link.
Your prompt
```
Add a section for the 2 test failures you just fixed, with the code before and after, and republish.
```
You should see the same link showing the new section, saved as a new version.
A new session made a second page instead?
Without the link, a new session starts a new artifact. Give Claude the link, or attach the page from /artifacts, then ask again.
In the /artifacts list, press o to open a page in your browser or c to copy its link.
Step 5: Turn comments into changes
4 min
Comments left on the page can come back to your session, so feedback turns into edits.
1. Ask teammates to comment on the page. An editor can send a thread to Claude with Send to Claude or by mentioning @claude.
2. In Claude Code, ask Claude to read the comments and make the changes. Try the prompt below.
3. Check the new version, then resolve the threads on the page.
Your prompt
```
Read the comments on [ARTIFACT LINK] and make the changes the commenters ask for.
```
You should see each comment thread listed in the terminal, then a new version of the page with the changes.
Claude says it can't read comments?
Comments need Claude Code 2.1.221 or later. Run claude update, start a new session and ask again.
Comments work on pages shared inside your organization. People with only the public link can't see or add them.