Overview
Claude Code can now turn session work into artifacts — live, shareable visual pages. Instead of constantly communicating status, your team can see work like incident investigations, code reviews, and dashboards as interactive web pages. Artifacts are built from full session context, including your codebase, connectors, and conversation.
Key features
-
Turn session work into live web pages
Technical work done in a session is hard to share as-is. Artifacts turn it into interactive web pages — PR walkthroughs, dashboards, incident timelines, checklists — so your team can see progress without a manual status update.
-
Create them by asking in your session
You create artifacts by asking for them. Prompt “Build an artifact listing every third-party dependency” or “Make an artifact walking through this PR,” and Claude Code generates the page from the context it already has.
-
Auto-updating with version history
When Claude Code updates an artifact, the open page refreshes in place at the same URL. Version history lets you restore at any time, and a gallery lets you browse and manage all artifacts.
-
Share across your org, private by default
An artifact is private to its author by default. You can share it with your teammates and your organization directly from the page, but it stays viewable only by authenticated members of your org and cannot be made public. Admins control access with an org-level toggle and role-based scoping.
-
Role-specific use cases
Artifacts cover work across roles: security findings that link to the exact line, a license audit of every dependency, a data-flow map tracking personal information, cloud resources and cost drivers mapped from Terraform, an incident timeline with suspect commits and an error-rate chart, and 5 UX variations of a signup form built from your component library.
Notes
- Beta for Claude Team and Enterprise — artifacts are currently available in beta for Claude Team and Enterprise orgs.
- Created from the CLI and desktop app — you build artifacts from the Claude Code CLI and desktop app, and the pages are viewable in any browser.
- Cannot be made public — artifacts are viewable only by authenticated members of your org and cannot be made public. Access is managed by admins.