# Move a Claude artifact out of the chat and onto its own link.

Ask Claude to publish the artifact to artifact.guru, or download it and drop it in. Then choose who can open it and see who did. Each change becomes a new version at the same link.

## Why move it out of the chat

An artifact stays in the chat that made it, where a client or a colleague without Claude can’t open it. They need a link, and you want a say in who opens it. When you fix something, the same link should show the fix.

Claude is good at interactive pages like the Port Avery map above, which has a delivery model inside. Once it’s published, the people you choose can open it in any browser, and it works just as it did in the chat.

## Two ways to get it out

1. **Ask Claude to publish it** Add artifact.guru once in Claude under **Settings → Connectors → Add custom connector**, with the address below. On Team and Enterprise, an Owner adds it and each member then connects. Then say “Publish this artifact to artifact.guru”. Claude sends the code and gives you the link.
2. **Or download it and drop it in** Download the artifact from Claude as a file, then drop it on your artifact.guru workspace. HTML pages and React components both work.

Connector address:

```
https://mcp.artifact.guru/mcp
```

> **React works too.** React artifacts publish unchanged, as a `.jsx` or `.tsx` file with a default export. React, Tailwind classes and npm imports load in the browser with no build step.

## Choose who can open it

| Mode | Who can open the link | Names in Views |
| --- | --- | --- |
| Private | People in your workspace | Yes |
| Email | People you invite, signed in with that address | Yes, and who hasn’t opened it yet |
| Secret code | Anyone with the link and the code | No, counts only |
| Public | Anyone with the link | No, counts only |

Each link also counts views and daily visitors, and shows where they came from and their devices.

Changing the mode never changes the link, so you can send it first and open it up later.

## Keep improving it at the same link

Ask Claude for a change and it edits the published file instead of making a new one. Each change becomes a version at the same address, and you can roll back from the Versions list. If a teammate works in ChatGPT or Codex, their agent can find and edit the same artifact.

## Limits

- Claude artifacts that call Claude from inside the page only work in Claude. Elsewhere, that part won’t respond.
- Pages run in the visitor’s browser, in a sandbox. Anything that needs a server or secret keys needs a real deployment.
- Shared links ask search engines not to index them, public ones included.

## Make your own

Have these ready:

- The artifact open in your Claude chat
- artifact.guru added as a connector

Then ask your agent:

```
Publish this artifact to artifact.guru as a private page. Keep the code
exactly as it is. Give me the link and tell me who can open it.

When I ask for changes later, edit the published artifact instead of
publishing a new one, so the link stays the same.
```

## Questions

### Do the people I share it with need a Claude account?

No. They open an artifact.guru link. Public and secret-code links need no account at all; invited people sign in with the address you invited.

### Can I make it public and still see who looked?

A public link shows counts, not names. To see who opened it, invite people by email instead.

### Does it work for artifacts made in other agents?

Yes. Codex, Gemini CLI, Grok and any custom MCP client publish the same way, and so does ChatGPT in Business, Enterprise and Edu workspaces ([how](https://artifact.guru/blog/publish-from-chatgpt)). Anything you can download as a file can be dropped in.

Source: https://artifact.guru/use-cases/claude-artifacts