TL;DR
Claude Code Artifacts (launched June 18, 2026; now on Pro, Max, Team and Enterprise per the Claude Code docs) turns a Claude Code session into a self-contained, live HTML page at a URL that updates as the session keeps working. You can publish it to a public link anyone can open with no sign-in (on Team and Enterprise an Owner has to switch that on), and on Team and Enterprise you can make a person in your org an editor. But comments and editing stop at the org line: people who only hold the public link can't see or add comments, and an editor has to be someone you add to the share dialog. There's still no custom domain, and it only works on what Claude itself built. If the person you need to reach is a client or a contractor with no Claude seat and you need them to do more than look, that's the gap this post covers.
What Claude Code Artifacts actually is
Anthropic describes it as a single, self-contained interactive HTML page published from a Claude Code session to a private URL on claude.ai, rendering in any browser and updating in place as the session continues: PR walkthroughs, system diagrams, dashboards, release checklists, the kind of thing that used to live only inside a terminal or a screen share. Boris Cherny, who leads Claude Code at Anthropic, called it "a game changer for how I work with Claude." For the job it's built for, watching a session's work update live for people already on your team, it's a real upgrade over pasting screenshots into Slack.
It's a different product from the artifact feature in the regular Claude.ai chat (what is a Claude artifact, explained here): that one now shares with specific people, your org, or "anyone with the link" (which needs a Claude sign-in for new artifacts; see the September 16 change). Claude Code Artifacts is scoped to a coding session, and its public link is the one that needs no sign-in.
The walls that are left
The biggest wall has come down: you can publish a public link, and on Team and Enterprise you can add editors. But the public link and the collaboration features are separate audiences, and the walls that matter for outside work are still up:
- The public link is view-only. Anyone can open it, but per the docs, "people whose only access is the public link don't see its comments and can't add any."
- Comments and editing stay inside your org. Comments are for people you share with inside your organization, and editors are added in the share dialog on Team and Enterprise. A client or contractor with no Claude seat isn't in either group.
- Editing runs through Claude. An editor updates the page by giving Claude the artifact's URL, and Claude republishes. It isn't a no-code canvas a non-coder can click into.
- Connector-backed pages lose their live data for public viewers. Anyone opening the public link without signing in sees the page without its live sections.
- No custom domain. The link lives on claude.ai, so a client deliverable can't carry your own brand.
OpenAI's ChatGPT Sites (first called Codex Sites) has since gone further on reach: its docs now describe a public option, invited outside viewers and custom domains. The pattern that holds across the model-makers is narrower than "internal only": each builds and hosts what its own tool made, and lets outside people look. Working on the page, as a client or contractor with no seat, is where the walls still are.
Comparison at a glance
| Claude Code Artifacts | ChatGPT Sites | Coedit | |
|---|---|---|---|
| Builds the app for you | Yes (from a Claude Code session) | Yes (from a prompt) | No, Coedit doesn't generate |
| Public "anyone with the link" | Yes, view-only (Owner must enable on Team/Enterprise) | Yes, where plan and admin allow | Yes |
| Editors | Yes, on Team/Enterprise, inside your org | Yes, active members of the owner's workspace | Yes, and public |
| Editing for people outside your org | No | No (visitors can't edit) | Yes |
| Custom domain | No | Yes, where available (not Enterprise at launch) | Yes, on paid plans |
| Comments on the live page | Inside your org only | Not described in the help article | Yes, for anyone |
| Non-coder editing | No | Yes, by describing the change to ChatGPT (owner and workspace editors only) | Yes |
| Works across tools (Claude, ChatGPT, Gemini, v0, Lovable, hand-written HTML) | Claude Code sessions only | Sites built in ChatGPT | Yes |
How Coedit fits
Keep building in Claude Code (or anything else). When the artifact needs to reach someone outside your Anthropic org, a client, a prospect, a contractor without a seat, export the page's HTML and paste it into Coedit. You get one link anyone can open with no account, comments pinned to the exact element, no-code editing for people you allow, and version history with rollback, on your own domain if you're on a paid plan. Claude Code Artifacts is the best way to watch a session build for your team. Coedit is the way to hand the result to everyone else.
FAQ
Q: Can I share a Claude Code Artifact with someone outside my company? A: Yes, if you publish a public link (on Team and Enterprise an Owner has to enable External sharing first). They can view it with no sign-in. They can't comment on it or edit it: comments are for people you share with inside your org, and editors are added in the share dialog. So an outsider can look, not work with you. To let a client or contractor without a Claude seat actually collaborate, move the page onto a tool built for outside collaboration.
Q: Does Claude Code Artifacts support a custom domain? A: No. Artifacts are hosted at a claude.ai URL with no option to serve them from your own domain.
Q: How is this different from a regular Claude artifact? A: The chat-based Claude.ai artifact is made in a conversation and, since September 16, 2026, shares by email, org or a link that needs a Claude sign-in (details here). Claude Code Artifacts is a separate feature scoped to a Claude Code session, with its own public link that needs no sign-in.
Q: What's the workaround to share a Claude Code Artifact externally? A: Export or copy the page's HTML and publish it through a tool built for external sharing, such as Coedit, which adds a public link, comments, no-code editing, and version history on top of whatever built the page.