Table of Contents
On June 18, 2026, Anthropic shipped Claude Code Artifacts (beta) — a feature that turns a terminal coding session into a "live" web page your team can share. Instead of Claude Code streaming endless git diff and logs as text, it can publish an annotated PR walkthrough, a self-updating dashboard, or an incident timeline as a single page.
This article covers what Artifacts is, how it differs from 2024's claude.ai Artifacts, how to use it, its limits, and availability — based on the official docs. Three takeaways up front. (1) It publishes a session's output as one page at a private claude.ai URL, and the content updates as the work progresses. (2) There is no dedicated /artifact command — you ask in plain language ("make a page that walks through this PR with annotations"). (3) For now it's a Team / Enterprise beta, usable only in sessions signed in via /login (not with an API key).
Turn a session into a "shared page"
— from terminal output to a live page you can look at and interact with
It publishes to a private claude.ai URL (viewable only by org members).
Each update becomes a new version at the same URL, and the page refreshes in place for whoever has it open.
1. What Claude Code Artifacts is
The official definition: "an artifact is a live, interactive web page that Claude Code publishes from your session to a private URL on claude.ai." Open it in a browser and it updates in place as the session continues. The page is "built from anything your session can reach, including your codebase and data it pulls through your connected tools" (MCP connectors).
The point is to "turn output that's hard to convey as terminal text into one page you can look at and interact with." For example, during a long investigation you can share an incident timeline that fills in as you work, or a release checklist that checks itself off as tasks complete. Anthropic positions it as collaboration tooling that "lets teams spend less time on status updates and more time building." Think of it as a new output surface for Claude Code, alongside Skills and MCP.
2. How it differs from 2024's claude.ai Artifacts
Many people will think of the side-panel (canvas) Artifacts that appeared in the claude.ai chat in 2024. They share a name and lineage, but Claude Code Artifacts is a different surface. Since the two are easy to confuse, here's the breakdown (note: this contrast is our own synthesis — Anthropic does not present them side by side).
| claude.ai Artifacts (2024) | Claude Code Artifacts (2026) | |
|---|---|---|
| Where it shows | A canvas beside the chat in claude.ai | A standalone page from a terminal coding session |
| Source of content | The chat conversation | The whole session (codebase, connectors) |
| Live-updating for viewers | No (you regenerate in chat) | Yes (published page refreshes in place) |
| Sharing scope | Can be made public | Org-only; cannot be made public |
In one line: the 2024 version "renders an artifact inside the chat," while the 2026 Claude Code version "turns a terminal coding session into a self-updating, org-shared web page." Same name, but different use case and a different way of sharing.
3. What it's good for
The use cases Anthropic names are exactly the kind where "seeing a page beats reading text."
When a "page" beats text
The common test: "is this output easier to look at and interact with than to read line by line?"
4. How to use it
The biggest quirk: there is no dedicated /artifact command. You ask in plain language, or Claude offers one when the output suits a page. The flow:
# 1) Ask in plain language during a session (examples)
Make an artifact that walks through this PR with the diff annotated inline.
Build a dashboard artifact of last week's deploy failures by service and keep it updated as you investigate.
# 2) Claude writes a .html (or .htm / .md) into your project and asks to publish
# "Claude wants to publish 'Deploy failures by service' (deploy-failures.html) to a private page on claude.ai" -> Yes
# 3) The URL is printed and opens in your browser. Reopen the latest with Ctrl+]
# Disable auto-open with CLAUDE_CODE_ARTIFACT_AUTO_OPEN=0To update, just ask Claude to revise — it edits the file and publishes to the same URL, with each publish recorded as a new version (you can restore older ones). To update from a different session, paste the artifact's URL (otherwise a new artifact is created). Share via the "Share" control in the page header to grant specific people or your whole org — a new artifact is visible only to you at first. Viewers must be signed in to claude.ai as members of the same org, and it's view-only (not co-edited — you remain the only writer). All your artifacts are listed in the gallery at claude.ai/code/artifacts.
5. Limits — it's not an "app"
The official docs state plainly: "an artifact is a capture of work, not an application." Misread that and you'll be disappointed, so note the constraints.
Main constraints (official)
· No backend: a single static page. It cannot store form input, call an API at view time, or serve multiple routes (in-page anchors only).
· No external requests: a strict CSP blocks external scripts/CSS/fonts/images plus fetch, XHR, and WebSocket. CSS/JS are inlined; images are embedded as data URIs.
· File types and size: only .html / .htm / .md. Rendered page must be ≤ 16 MiB (large images are the usual cause of failed publishes).
· Token cost: inlined CSS/JS and data-URI images mean it consumes more tokens than terminal text.
So Artifacts is not "a way to build a running app" — it's "a way to solidify a session's output into one shareable, readable page." If you need a real tool that talks to external services, go to normal development and deploy. To share outside your org, have Claude output the raw HTML file (sharing stops at the org boundary).
6. Availability and admin controls
As of June 2026 the scope is limited (it's a beta — confirm the latest in the docs).
| Item | Details |
|---|---|
| Plans | Team / Enterprise only (not Pro/Max). On by default on Team; an admin enables it on Enterprise |
| Status | Beta (shipped June 18, 2026) |
| Where it works | Claude Code CLI, or the Claude desktop app (v1.13576.0+). Off by default in Agent SDK / GitHub Action / MCP-server contexts |
| Auth | Must be signed in to claude.ai via /login. API keys, gateway tokens, and cloud credentials cannot publish |
| Model provider | Anthropic API only (not Amazon Bedrock / Google Vertex / Microsoft Foundry) |
| Org policy | Disabled for orgs with CMEK, HIPAA, or Zero Data Retention (ZDR) |
For admins there are org-level on/off, role-based scoping (Enterprise RBAC), retention policies, an audit log (claude_artifact_*), and a Compliance API. To disable it yourself, use "disableArtifact": true in settings, the env var CLAUDE_CODE_DISABLE_ARTIFACT=1, or deny the Artifact permission. If you get stuck on sign-in, see auth / login error fixes.
Summary
Claude Code Artifacts (June 18, 2026, beta) turns a terminal coding session into a "live" shared page at a private claude.ai URL. PR walkthroughs, dashboards, incident timelines, checklists — output that's easier to see than to read — shared within your org. It's distinct from 2024's canvas-style claude.ai Artifacts: session-sourced, self-updating, org-only. There's no /artifact command — you ask in plain language, Claude writes a .html and publishes, and each update is a new version at the same URL.
But it's "a capture of work, not an app" — no backend, no external requests (CSP), a single page, ≤ 16 MiB. Usage is a Team / Enterprise beta requiring /login sign-in (not API keys) on the Anthropic API only (not Bedrock, etc.). For teams that want to cut the cost of status updates, it's a strong option. Related: Claude Agent Skills, MCP, Claude Cowork.
FAQ
Q. Is this the same as the 2024 claude.ai Artifacts?
A. No, it's different. The 2024 version renders an artifact in a canvas beside the chat in claude.ai. Claude Code Artifacts turns a terminal coding session into a standalone page at a private claude.ai URL, built from the whole session (codebase, connectors), self-updating, and org-only. They share a name and lineage, but the surface and the way of sharing differ.
Q. How do I create one? Is there a command?
A. There is no dedicated /artifact command. Ask in plain language during a session ("make an artifact that…"), or Claude offers one when the output suits a page. Claude writes a .html (or .htm / .md), asks permission to publish, and prints a URL when you approve. Reopen the latest with Ctrl+].
Q. Can anyone view the page? Can I make it public?
A. It's org-only; you can't make it public. A new artifact is visible only to you at first; use Share in the page header to grant specific people or the whole org. Viewers must be signed in to claude.ai as members of the same org, and it's view-only. To hand it outside the org, have Claude output the raw HTML file.
Q. Can I build a working web app?
A. No. The docs call an artifact "a capture of work, not an application." It has no backend, no external requests (a CSP blocks fetch/XHR/WebSocket), a single page, and a ≤ 16 MiB limit. If you need form storage or API calls, build and deploy normally. Artifacts is specialized for "sharing output in a readable form."
Q. Can I use it on my plan?
A. As of June 2026 it's a Team / Enterprise beta (not Pro/Max). On by default on Team; an admin enables it on Enterprise. You need a session signed in to claude.ai via /login, and API keys / cloud credentials cannot publish. The provider is the Anthropic API only (not Bedrock/Vertex/Foundry). Scope can change, so confirm the latest in the official docs.
