Anthropic is extending Claude Code with artifacts, giving teams a way to turn the output of a coding session into an interactive web page. The feature is already familiar from Claude chat, but its arrival in Claude Code makes it more directly useful for software work, team review, and shared technical context.
What Claude Code artifacts do
Artifacts in Claude Code let a user take the results of a Claude Code session and present them as a live, shareable page. The page is built from the full session context, including code, connected tools, and chat history.
That matters because a coding session often contains more than a final answer. It may include the path taken through the code, the tools used along the way, and the discussion that shaped the result. Claude Code artifacts package that material into a visual format that others can open rather than forcing them to reconstruct the session from scattered notes or messages.
Anthropic says the page updates automatically at the same URL when something changes. It also includes version history, so the artifact is not only a static snapshot of one moment. It can reflect the ongoing state of the work while preserving a record of earlier versions.
How teams create and share an artifact
The workflow described by Anthropic is simple: during a Claude Code session, the user asks for an artifact or asks for something visual. Claude Code then returns a link.
That link can be opened in a browser or in the desktop app. From there, it can be shared directly through the header, giving teams a route from a coding session to a page that colleagues can view.
The source article describes artifacts as interactive web pages, which means the feature is positioned as more than a text export. It is meant to turn session results into something that can be inspected and used by others, especially when the output is easier to understand visually.
Where artifacts fit in software work
Anthropic says use cases include PR walkthroughs, incident timelines, license audits, and architecture overviews. Those examples point to a common theme: software teams often need to explain complex work clearly to people who were not present for the original coding session.
A PR walkthrough can benefit from a structured page that shows what changed and why. An incident timeline can benefit from a shared view of sequence and context. A license audit can benefit from a page that gathers relevant findings. An architecture overview can benefit from a visual summary that connects code, tools, and discussion.
The feature also changes the role of the coding session itself. Instead of being only a private interaction between a developer and Claude Code, the session can become a source of team-facing documentation. The artifact is generated from the session context, so the page can carry forward the reasoning and materials that informed the work.
Privacy and admin controls
Anthropic says artifacts are private by default. They are visible only to authenticated members of the user’s organization.
That default is important for team coding workflows because session context can include code, connected tools, and chat history. The source article does not describe public sharing as the baseline. Instead, it presents artifacts as an organization-scoped feature with administrative controls.
Admins can control access through roles and retention policies. That gives organizations a way to decide who can view artifacts and how long the related material should be retained, based on the controls Anthropic makes available for the feature.
Availability for Claude customers
The feature is available as a beta for Claude Team and Enterprise customers. It works with both the Claude Code CLI and the desktop app.
That means the same artifact concept can fit into different Claude Code workflows. A user working through the Claude Code CLI can create and share an artifact, and a user working through the desktop app can also use the feature.
For teams already using Claude Code, artifacts add a clearer handoff mechanism. A session can produce not only code-related output, but also a live page that teammates can open, review, and revisit as the work changes.