01
The one-sentence version
You know how a Google Doc link always shows the latest version, so you never resend the file? Claude Code Artifacts does that for the work an AI does for you — but you never build or edit the page. When a Claude Code session finishes a piece of work, it can publish the result as a live, interactive web page at one permanent link. As the session keeps going, it republishes that same page in place — a fresh version each time, with full history. Anyone on your team opens the link and always sees the latest, instead of you pasting a new screenshot into Slack every hour.
Read this first — who can actually use it. Artifacts launched on June 18, 2026 as a beta for Claude Team and Enterprise organisations only. It is not on Free or Pro plans yet. And the page is private to your organisation — viewable by authenticated org members, not a public URL. If you're on Free or Pro, this is a "watch this space," not a "use it today."
02
What actually happens, step by step
- You run a Claude Code session as normal — building, reviewing, investigating.
- Claude Code publishes the output as an Artifact — a live web page at a permanent link, built from your full session context (no manually wiring up a data source).
- You share that one link with your team. Authenticated teammates in your org open it in any browser.
- The work continues, the page republishes in place. Same link; teammates with it open see the update the moment it's published.
- Every publish is a new version at the same link — with version history, so you can restore an earlier one at any time.
It's session-driven, not a background daemon: the page updates when Claude Code publishes a change during the session — not on a continuous live feed of its own.
03
Five things worth publishing first
The pattern that wins: anything your team currently keeps re-pasting as a screenshot or a "latest status" message is a candidate. From Anthropic's own launch examples:
- A PR walkthrough / code-review page — what changed and why, that updates as the branch lands.
- A live progress dashboard — filterable, sortable, current without anyone refreshing it by hand.
- A release checklist that fills itself in — the boxes tick as the work completes.
- An incident timeline — investigation steps and error-rate charts, building in real time.
- A project status page — the morning question "what got done?" already answered when you open it.
04
Availability, in plain terms
| Plan | Artifacts (beta) today? |
|---|---|
| Claude Free | No — not available yet |
| Claude Pro | No — not available yet |
| Claude Team | Yes — in beta |
| Claude Enterprise | Yes — in beta |
Available from the Claude Code CLI and the desktop app; the published page is viewable in any browser by authenticated members of your organisation. Beta details and rollout can change — check the official post (linked below) for the current state before you plan around it.
05
Why this matters if you build or resell with AI
The quiet shift here isn't "AI writes a web page." It's that the output of an AI session becomes a shared, living artefact your team and clients can watch — not a static deliverable you re-export every time something changes. If you run AI work for clients, "here's a live link you can check any time" is a better experience than "I'll send you an updated file." Even before you're on a plan that has it, it's worth understanding the shape of where agent tooling is going: from one-off outputs to always-current, shareable surfaces.
If you want to turn "I run AI for businesses" into something you sell under your own brand, the Reseller Kit is the natural next step.
The 75-second version
Get the next drop
New AI build guides + the occasional bonus template. No spam, unsubscribe anytime.
By submitting you agree to our Privacy Policy & Terms. Unsubscribe anytime.
You're in — check your inbox to confirm.
Frequently asked questions
What is Claude Code Artifacts?
A feature that publishes a Claude Code session's output as a live, interactive web page at one permanent link. As the session continues, the same page republishes in place — a new version each time, with full version history so you can restore an earlier one.
Can anyone use it right now?
No. At launch (June 18, 2026) Artifacts is in beta for Claude Team and Enterprise organisations only. It is not available on Free or Pro plans yet.
Is the link public?
No. The page is private to your organisation — viewable by authenticated members of your org, not a public URL anyone can open.
Does the page really update by itself?
It republishes when Claude Code publishes an update during the session. Teammates with the page open see the change the moment it's published. It's session-driven, not an always-on background daemon.
What should I publish as an Artifact first?
A PR walkthrough, a live progress dashboard, a release checklist that fills itself in, an incident timeline, or a project status page — anything a team currently keeps re-pasting as screenshots.
Sources · Anthropic — Artifacts in Claude Code (official announcement) · Claude Code docs — share session output as artifacts · Verified 2026-06-20 against the official post + multiple independent reports (VentureBeat, TechTimes, DevOps.com).