TL;DR
Claude Code Artifacts (beta, launched June 18, 2026, on Team and Enterprise plans) turns a Claude Code session into a self-contained, live HTML page at a URL that updates as the session keeps working. It's built for teammates, not clients: the page is visible only to authenticated members of the same Anthropic org, and Anthropic says explicitly it cannot be made public. No custom domain, no comments, no editing by the viewer. If the person you need to reach isn't in your org, this feature can't get the page to them; 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 is a chat-published output anyone can generally view with a link; Claude Code Artifacts is scoped to a coding session and an organization.
The wall: it can't leave your org
This is the part that matters for anyone building for a client, a prospect, or the public:
- Viewers must be authenticated members of the same org. There's no anonymous, "anyone with the link" view.
- It cannot be made public, by design, not as a missing checkbox waiting on a future release.
- No custom domain. Even inside the org, the link lives on claude.ai.
- No comments pinned to the page. Feedback still routes back through chat, Slack, or a meeting.
- No editing for the viewer. A teammate watching the artifact update can't change a word on it themselves.
That's the same shape as Codex Sites, OpenAI's equivalent feature: both companies built "share this build with my team," and both stopped exactly at the company's edge. It's a sensible scope for an internal-tooling feature. It's also a hard wall the moment your actual audience is outside it.
Comparison at a glance
| Claude Code Artifacts | Codex Sites | Coedit | |
|---|---|---|---|
| Builds the app for you | Yes (from a Claude Code session) | Yes (from a prompt) | No, Coedit doesn't generate |
| Viewers need an org account | Yes, always | Yes, always | No |
| Public "anyone with the link" | No, explicitly disallowed | No | Yes |
| Custom domain | No | No | Yes, on paid plans |
| Comments on the live page | No | No | Yes |
| Non-coder editing | No | No | Yes |
| Works across tools (Claude, ChatGPT, Gemini, v0, Lovable, hand-written HTML) | Claude Code sessions only | Codex output only | 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: Not as published. Viewing requires being an authenticated member of the same Anthropic org, and Anthropic states the page cannot be made public.
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 published from a conversation and generally viewable via a link (details here). Claude Code Artifacts is a separate, newer feature scoped to a Claude Code session and locked to your organization.
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.