Claude Code Can Now Share Live Pages of a Session

Anthropic has added Artifacts to Claude Code, letting you turn the result of a coding session into a live, shareable web page. You ask for an artifact during a session and get back a link that opens in a browser or the desktop app. The page is built from the full session context — the code, the connected tools, and the chat history — and when the underlying work changes, the page updates at the same URL while keeping a version history. The feature launched on June 18, 2026, in beta for Claude Team and Enterprise customers, and works with both the Claude Code CLI and the desktop application.

The framing Anthropic gives it is sharing, not coding. The examples it points to are the things engineers normally write up by hand after the fact: a walkthrough of a pull request, a timeline of an incident, a license audit, an overview of a system's architecture. In each case the artifact is generated from what actually happened in the session, so the page is a record of the work rather than a fresh document someone has to assemble and keep in sync.

How access works

Artifacts are private by default and visible only to authenticated members of your organization — they are not public links you can paste anywhere. Administrators manage who sees what through roles and retention policies, which is the part that makes this usable inside a company rather than just a neat demo. As Anthropic puts it, "the pages are generated from the full session context: code, connected tools, and chat history." That is also the line to read carefully: whatever was in the session is what ends up on the page.

Why it matters

The hard part of working with a coding agent has never been getting it to do the work — it is explaining to a teammate, a reviewer, or your future self what the agent did and why. Normally that means screenshots, a hand-written summary, and a paragraph in Slack that goes stale the moment the code moves on. An artifact collapses that into one link that stays current. If you run a small team, or you are the person who keeps getting asked "wait, what did this change actually do," that is a real chunk of busywork removed.

The catch is the same as the benefit: the page carries the session context, so anything sensitive that passed through the chat — keys, internal URLs, customer data — can land on a shareable page. Private-by-default and admin controls help, but they only help if the controls are set before the link goes out.