Claude Code Adds Artifacts: Live, Shareable Pages for PR Walkthroughs and Dashboards
Artifacts in Claude Code turn an in-progress session into a live web page that updates as the session works. Launched in June 2026 as a beta for Team and Enterprise with org-only sharing, they are now on Pro, Max, Team, and Enterprise, and an artifact can be shared to a public link anyone can open.
Claude Code now supports Artifacts: live web pages generated from a Claude Code session that you can keep private, share inside your organization, or publish to a public link. They launched in June as a Team and Enterprise beta; Anthropic has since extended them to Pro and Max and let them call MCP connectors for live data. Anthropic frames the feature as a way to turn a session's work into something other people can understand at a glance, without needing a meeting to narrate what the agent found.
Key Takeaways
- Artifacts turn an in-progress Claude Code session into a live, shareable visual page such as PR walkthroughs, dashboards, and release checklists.
- Pages refresh as Claude Code republishes updates, so teammates see changes at the same link.
- Artifacts are private by default. On Team and Enterprise you can share with specific people or your whole organization, and on every plan an artifact can go to a public link (off on Team and Enterprise until an Owner turns on External sharing).
- Availability: Pro, Max, Team, and Enterprise, from the Claude Code CLI or the Claude desktop app. At launch it was a beta for Team and Enterprise only.
What Anthropic Means by "Artifacts" in Claude Code
Anthropic says Claude Code can "capture work progress as an artifact," turning Claude Code's work into "live, shareable visual pages" that update as the session works. The examples they call out include PR walkthroughs, system explainers, dashboards, and release checklists.
In other words: instead of shipping a wall of terminal output or a long markdown summary, Claude Code can publish an interactive page someone else can open and explore.
How Sharing Works
Anthropic describes artifacts as private to their author by default. When you're ready, you share an artifact from the Share control in the page header.
Who you can share with depends on your plan. The Claude Code docs now describe two audiences. Within your organization, on Team and Enterprise plans, you grant access to specific people or to everyone, and viewers sign in to claude.ai as members. Publicly, you share a link anyone on the internet can open with no claude.ai sign-in; on Team and Enterprise this is off until an Owner turns on External sharing under Organization settings > Artifacts. On Pro and Max, artifacts are private to you until you share them. (Claude Code docs, artifacts)
At the June launch, Anthropic's announcement said artifacts were viewable only by authenticated members of your org and could not be made public. That is no longer the case.
Versioning and Ongoing Updates
A key part of the pitch is that artifacts change as the agent keeps working. Anthropic says that when Claude Code updates an artifact, "the open page refreshes in place and teammates see the updates the moment they're published."
They also describe versioning: each publish creates a new version at the same link, with version history available to restore prior versions.
Why This Matters for Day-to-Day Dev Work
Claude Code is already good at doing a bunch of work while you wait: debugging, incident investigation, PR review prep, summarizing complex code paths. The bottleneck is often the handoff. If one engineer runs the session, everyone else needs a synchronous walkthrough to trust what happened.
Artifacts target that gap by giving the session a shareable output surface. Anthropic's incident example is straightforward: a single page can combine connected tool signals (like monitoring charts) with repo context (tests, functions, commits) and the agent's reasoning, then get republished as the investigation evolves.
Corrections and Updates
- October 9, 2026: This page said artifacts were a beta for Team and Enterprise organizations only, viewable only inside your organization, and could not be made public. The Claude Code docs now list Pro, Max, Team, and Enterprise plans and describe sharing to a public link that anyone can open, off on Team and Enterprise until an Owner enables External sharing. (Claude Code docs, artifacts)
Sources
- Claude (X): https://x.com/claudeai/status/2067671912038240487
- Anthropic blog, "Claude Code now supports artifacts," June 18, 2026: https://claude.com/blog/artifacts-in-claude-code
- Anthropic, Claude Code docs, "Artifacts," checked 2026-10-09 (plans, sharing audiences, External sharing, versions): https://code.claude.com/docs/en/artifacts
- Video: https://www.youtube.com/watch?v=m7TJqx8CYG8
Read next
Related coverage- Claude Code
Claude Code Artifacts Expand to Pro and Max Plans (Private Until You Share)
Claude Code Artifacts, which launched for Team and Enterprise, reached Pro and Max plans in July 2026. On Pro and Max an artifact is private until you share it, and a public link is the way to share it; sharing with specific people or a whole organization is a Team and Enterprise feature.
- Claude Code
Claude Code artifacts can now call MCP connectors for live, viewer-specific data
Claude Code artifacts can call MCP connectors each time someone views them, so a published page shows current data rather than a session snapshot. Available on Pro, Max, Team, and Enterprise plans with Claude Code v2.1.209 or later. A connector-backed page can now go to a public link, but its live sections stay empty for signed-out or outside viewers.
Frequently Asked Questions
Who gets access to Artifacts in Claude Code?
As of October 2026, the Claude Code docs say artifacts are available on Pro, Max, Team, and Enterprise plans, from the Claude Code CLI or the Claude desktop app, in a session signed in with /login. At the June launch Anthropic offered them in beta to Team and Enterprise organizations only.
Can Claude Code artifacts be shared publicly?
Yes, as of October 2026. Artifacts start private to their author. The docs now allow a public link anyone can open without signing in; on Team and Enterprise it stays off until an Owner turns on External sharing. Sharing with specific people or your whole organization is Team and Enterprise only.
What types of outputs work well as artifacts?
Anthropic's examples include PR walkthroughs, system explainers, dashboards, and release checklists that update as the session does work.