Anthropic announced a new feature for Claude Code today. Thariq from the Claude Code team posted it on X: Claude Code can now upload and edit HTML artifacts that you share with your team or with other Claudes. The official @claudeai account put it cleanly alongside: interactive pages, built from your session, shared with your team through a private link. The feature is called Artifacts and it runs in beta on the Team and Enterprise plans.
What it is
You may already know Artifacts from Claude itself, the chat in your browser. There you type a question and sometimes get a working thing back, a calculator, a chart, a small piece of interface that runs right away. What is new is that Claude Code, the version that lives in your terminal and your editor, can now do the same. The difference is the source. An artifact from Claude Code is built from your work session. Not from a single stray question, but from the work you just did.
The examples Anthropic gives make it concrete. A walkthrough of a pull request, so a colleague sees in a single page what changed and why. Or a living project dashboard that moves with where the project stands. Not a static export, but an interactive page where the buttons work, the forms accept typing and the charts respond.
How it works
The idea is simple. You work with Claude Code on something, and at the end there is a page you share. Not as a file you email around, but as a private link. Whoever opens the link sees the page exactly as intended, with everything in place.
The note that you share it with “your team or other Claudes” is the part that struck me most. An artifact is then not only something for people to look at, but also something a next Claude session can pick up as a starting point. The page becomes a handoff point, between you and a colleague, or between two pieces of work.
How they use it at Anthropic themselves
What makes the idea tangible is the people who built it. Boris Cherny, one of the creators of Claude Code, shared what he uses Artifacts for. His list is a good guide for what you can do with it yourself:
- Visual explanations of tricky code. A piece of code that is hard to follow gets turned into a page that shows step by step how it works. Useful to grasp it yourself, or to explain it to someone else.
- System diagrams. How do the parts of your project fit together? Claude builds a diagram of it that you share, instead of drawing it by hand.
- Quick previews of options. Cherny has Claude put a few animation variants side by side, so you see in a single page which one works best before you choose.
- Data analyses and dashboards. An analysis or dashboard he shares with the team, as a living page rather than a loose export.
“They are a game changer for how I work with Claude,” he writes. That is not company marketing, but the experience of someone using the tool himself. And it makes clear right away that Artifacts is not one trick, but a way to cast almost any piece of work into a shareable form.
For whom, and when
Right now Artifacts is in beta, and only on the Team and Enterprise plans. That is a deliberate choice. On those plans you can only share an artifact within your own organization, not publicly on the web. Whoever opens the link has to sign in with an account from that same Team or Enterprise. So it stays within your company’s walls.
Thariq writes that Pro and MAX are coming “soon.” Anthropic gives no date. If you work solo or in a small team on Pro, that means waiting a little longer for now.
Why this matters
The thread running through what Anthropic shipped over the past six months is clear: the work is shifting from making things yourself to instructing, checking and handing off. Artifacts fits right into that. The step it removes is the handoff. You no longer have to write a separate document about what you did, because the page you share is the work itself, in a form another person grasps immediately.
For teams working with Claude Code that can save a lot. A PR walkthrough that builds itself from the session is faster than a review note you type afterward. And a dashboard that moves with the project is something other than a screenshot that is outdated again the next day.
What stood out to me
Two caveats I want to put down honestly.
The first is about the wall between the plans. That Artifacts starts on Team and Enterprise makes sense, since those are the places where people work in groups. But it also means the people who lean hardest on sharing, the solo builders and small teams on Pro, cannot get to it yet. “Soon” is a stretchy word. Until then this is a feature for the bigger wallet.
The second is about what a shared page actually is. An artifact from your session can contain code, data or reasoning you do not simply want outside your team. That it stays within the organization and sits behind a login is exactly the right call. But it does place a responsibility on the maker: before you forward a link, know what is on it. A working page shares more easily than a loose file, and that ease is a reason to look carefully.
These are caveats, not objections. Artifacts makes sharing work from Claude Code a good deal more natural. What you made now no longer sits only in your terminal, but on a page another person can open right away. And once it reaches Pro and MAX, it will be there for the rest as well.
Honestly, I cannot wait to use it myself and try out a whole range of use cases. A PR walkthrough, a dashboard, a handoff to a next session: I am curious where it makes the difference in practice. And you? What would you build with Artifacts first?
This piece also appeared in Dutch: Claude Code krijgt Artifacts: deel een werkende pagina uit je sessie.