A page instead of the terminal

What it is and why it matters

You work with Claude Code for an hour and the result is in the terminal: lines of text, tables made of dashes, a diff three screens long. That's fine for you. But your co-founder, your client or whoever reviews your code won't read it, and you end up pasting pieces into a chat, ten messages one after another.

Artifacts fix this. An artifact is a real web page that Claude Code publishes from your session to a private address on claude.ai. Inside is the work of the session: a comparison of options, a chart, an annotated diff, a checklist that gets ticked off while Claude works. You open it in the browser, and when Claude republishes it, it updates in place, even for people who have it open.

Use one when something is easier to understand by looking at it than by reading it line by line. And know what it isn't: it's a single static page with no server behind it. It can't have several linked pages, it can't sign people in with an account, it doesn't store data. It isn't your website. For an internal tool with a backend (the part that runs on a server and stores the data) you need to put it online on your own servers.

1. What you need

Artifacts only work when every one of these conditions is true. If one is missing, Claude writes an HTML file on your computer or tells you it can't publish.

• A Claude subscription: Pro, Max, Team or Enterprise. On Team and Enterprise they're on by default, but an Owner (whoever runs the organization) can turn them off for everyone.
• Signing in with your claude.ai account: in Claude Code, type /login. A session that uses an API key, a gateway token or cloud provider credentials can't publish.
• Claude through the Anthropic API. Artifacts aren't there if you use Claude from Amazon Bedrock, Google Cloud or Microsoft Foundry.
• No special data rules in your organization: if customer-managed encryption keys (CMEK), HIPAA or Zero Data Retention (no data kept) are enabled, artifacts aren't there.
• Claude Code in the terminal or in the Claude desktop app, on the latest version. They're off by default when you run Claude Code with -p from your own scripts and in the Agent SDK.

2. How to ask for one

You don't need a command. You ask in plain words: say “artifact” or “page” and describe what you want to see. Sometimes Claude publishes one on its own, when it sees the result reads better as a page. Here are the four prompts I use most, ready to copy. Replace the parts in [ ] with yours.

Make me an artifact with three different versions of [the welcome screen], side by side. Make them genuinely different from each other and under each one write in one line what I gain and what I lose.

Turn this plan into an artifact with a checklist. While you work, tick off the items you finish, add a note for the ones you skip and republish to the same link.

Make me an artifact that walks through this pull request: show the diff with margin notes next to the lines that matter and color-code the issues by severity.

Make me a dashboard artifact with the data you've already gathered in this session: [last week's errors], broken down by [service]. Keep it updated while you investigate.

Claude writes the page to an HTML or Markdown file, in a temporary folder outside your project, publishes it, prints the link and opens it in your browser. It picks the title and the tab icon itself: if you want different ones, ask. At first, only you can see it.

3. How to find it again

• Ctrl+] reopens the session's most recent artifact at any time.
• A small pill under the prompt shows the page's name, or how many there are if the session has more than one.
• /artifacts lists your pages and the ones shared with you, with this session's at the top. Pick one and press o to open it in the browser, c to copy the link, Enter to attach it to the session you're in (if it's already attached, it opens it).

The list comes from your claude.ai account, so it also works in a new session or after /clear, when the link has scrolled out of the terminal. Every page you've created is also in your gallery, at claude.ai/code/artifacts.

4. How to share it

A new page is private: only you can see it. To show it to others, open it in the browser and use the Share control at the top of the page. Who you can share it with depends on your plan:

• With Pro and Max, the personal plans, you create a public link: anyone can open it, even without a claude.ai account.
• With Team and Enterprise you give it to specific people in your organization or to the whole organization. Whoever opens it signs in to claude.ai with the organization account.
• On Team and Enterprise the public link is off until an Owner turns on External sharing in Organization settings > Artifacts. If they turn it off again, the public links already sent stop opening.

Every publish is kept as a version. From the same Share control you choose which version the others see: a specific one, or always the latest. That way Claude can keep working on the page without showing the half-finished steps.

5. How to keep it updated

To change it, just ask: Claude edits the file and republishes to the same address. Anyone with the page open sees the update in place, and you don't have to send a new link.

Add [the breakdown by country] under the chart and republish.

From a new session it's different. If you only say “update the page”, Claude creates another one. Give it the link, or attach the page from /artifacts:

Update [the artifact's link] with today's numbers.

If you share it within your organization, the people who see it can leave comments on the page, and you can ask Claude to read them and make the changes. Anyone who can edit it can also send one straight to Claude, with Send to Claude or by writing @claude. People who only have the public link don't see the comments.

And if you want the numbers to update by themselves every time someone opens the page, without Claude republishing it, the page can call the connectors of your claude.ai account, GitHub for example. That's one more step: I explain it in the DASHBOARD guide (strikt.fit/dashboard-live).

Common mistakes

• Sending the link before sharing the page. A new page is private: if you don't go through Share and choose who sees it, the others can't open it.
• Treating it as your website. It's one static page: no login, no form that stores data, no links to other pages (relative links don't work). For that you need a real website.
• Asking to “update the page” in a new session without giving the link. Claude creates another one, and you end up with two different pages out there.
• Putting data you don't want circulating behind a public link. Anyone who has the public link can open it: leave out keys, customer data and internal numbers, or share only within your organization.
• Filling it with heavy images. The page must stay under 16 MiB and images embedded in the page use a lot of tokens: for charts and diagrams, ask for SVG or HTML.

Checklist

• I'm on a Pro, Max, Team or Enterprise plan and signed in with /login, not with an API key
• I asked for the page by describing what I want to see, and Claude gave me a link
• With Ctrl+] or /artifacts I find the page again even when the link has scrolled out of the terminal
• Before sending the link I used Share and chose who sees the page
• I chose which version of the page the others see
• The public link contains no keys, customer data or internal numbers
• To update it from a new session I give Claude the page's link

Frequently asked questions