---
title: "The Claude Code artifacts alternative – Publish from any agent"
description: "Publish HTML and Markdown from any agent to a private URL. It works from Claude Code on Bedrock or with an API key. Colleagues sign in with no Claude seat."
---

# The open alternative to Claude Code artifacts for pages from any agent

Publish HTML and Markdown from any coding agent to a private URL. This works when Claude Code runs on Bedrock or Google Cloud, or with an API key. Colleagues sign in to read the page, and they need no Claude seat.

[Start free](https://app.display.dev/) · No card required · Viewers and commenters are free

Kestrel's Q3 churn review, an HTML report with its own layout and chart, open on Display. The version history lists four versions at the same URL. Claude Code published v1 for Ana Ruiz. Codex published v2 for Ben Okafor. Priya Shah edited v3 on the page. Cursor published v4 for Maya Lind. Version 4 answers Priya's comment “Can we split EMEA out?”

## Should I use Claude Code artifacts or Display?

Use Display when the Claude Code session cannot publish an artifact. That is Claude Code on Amazon Bedrock, Google Cloud or Microsoft Foundry, or with an API key or a gateway token. Also use it when Cursor or Codex made the page, or when colleagues without a Claude seat must sign in to read it. Display Team costs $59 a month, billed yearly, for the whole company, and viewers are free. Keep Claude Code artifacts when you sign in to Claude Code with a claude.ai account and your readers are members of your Claude organization, or a public link is acceptable. They are built in and cost nothing more.

## Claude Code artifacts and Display compared: sessions, sign-in and price

A Claude Code artifact is a web page that Claude Code publishes from your session to a private URL on claude.ai. Display publishes the same HTML or Markdown page from any agent.

| | Claude Code artifacts | Display |
|---|---|---|
| **Bedrock, Google Cloud or Foundry sessions** | No – claude.ai sign-in needed | Yes – Any model provider |
| **API-key and gateway sessions** | No | Yes |
| **Publish from Cursor or Codex** | No – Claude sessions only | Yes – CLI, MCP or API |
| **Colleagues behind sign-in** | Partly – Organization members only | Yes – Google, Microsoft or email |
| **50 colleagues behind sign-in, per month** | $1,000, billed yearly | $59, billed yearly |
| **Outside people behind sign-in** | Partly – Beta, Claude account needed | Yes – Email invite with a role |
| **CI and headless runs** | Partly – Off by default | Yes – With an API key |
| **Public link without sign-in** | Yes | Yes |
| **External images on the page** | No – Embedded images only | Yes |
| **Size limit** | 16 MiB rendered page | 50 MB a file on paid plans |
| **Versions at one URL** | Yes – With a version picker | Yes – Restore on paid plans |
| **Send a comment to the agent** | Yes – @claude, for editors | Partly – Agent reads them when asked |
| **Live data through connectors** | Yes – Each viewer's own account | No |
| **No added cost** | Yes – Included in paid Claude plans | Partly – Free plan, paid from $9 a month billed yearly |

Checked 11 November 2026. Sources: [Claude Code artifacts](https://code.claude.com/docs/en/artifacts) · [Share artifacts](https://support.claude.com/en/articles/9547008-share-artifacts) · [Claude pricing](https://claude.com/pricing)

## From a local file on one laptop to one list of pages from every agent

Ana publishes an artifact from Claude Code. Maya runs Claude Code on Bedrock and gets a local file. Ben builds in Cursor. Display holds all three pages, with one way to share.

- **Before:** Split by tool and session
- **After:** One place for every agent

Company pages open for everyone at Kestrel with Google or Microsoft sign-in.

## Open to every agent, session and colleague

You publish without a claude.ai sign-in, and colleagues sign in to read without a Claude seat.

- **Publish from any session** – Cursor, Codex, Claude Code or any other agent publishes through the CLI, MCP or the API. Display does not check which model provider or sign-in the session uses. A CI run publishes with an API key.
- **Sign in without a seat** – On Solo and higher plans, colleagues sign in with Google or Microsoft. On every plan, they can use a one-time password. Viewers and commenters are free.
- **Comments go back to the agent** – A colleague selects text and comments. When you ask, your agent reads the comments, publishes the next version at the same URL and resolves the threads it answered.

## Edit any document in-line.

Fix any line right where you read it.

1. Select Edit on the page
2. Change it on the page
3. Save – the next version at the same URL

## Share each page behind sign-in, with no seat for readers

A page stays private until you share it. Then choose who can open it – one page, a folder or a whole Space.

- **Private by default** – Every page stays private until you share it with people and groups.
- **One-click sign-in for colleagues** – On Solo and higher plans, colleagues use the Google or Microsoft account they already have.
- **Invite people outside your company** – Invite clients and partners by email, and give each one a role: Viewer, Commenter, Contributor or Editor.
- **Know who opened it** – On Team and Business, see who opened which page, and when, before you follow up.

## Claude Code artifacts or Display?

Many teams use both. Choose by how the session signs in and who has to read the page.

### Keep Claude Code artifacts for

- Sessions where you sign in to Claude Code with a claude.ai account.
- Readers who are members of your Claude organization, or pages that can be public.
- Pages that pull live data through each viewer's own connectors.
- Comments that an editor sends to Claude with @claude.
- Claude's Slides, Design and Docs templates, which are in beta.

### Use Display for

- Claude Code on Bedrock, Google Cloud or Foundry, or with an API key or a gateway token.
- Pages from Cursor or Codex.
- Reports that a CI run publishes with an API key.
- Colleagues who must sign in to read the page but have no Claude seat.
- Pages that load images from other sites, or scripts from outside Claude's five allowed CDN hosts, and files up to 50 MB on paid plans.

> “We gave it to a few people, expecting the super users who’d been asking for a publishing platform. We didn’t realize the whole business would pick it up.”
>
> – Rory Powell, IT and AI Ops Manager, Kogan.com

**Free plan: $0.** 3 pages behind sign-in and unlimited public pages. No credit card required, and viewers stay free.

[Start free](https://app.display.dev/)

## A full workspace behind every URL

### Spaces and folders

A Space for every team, with folders inside and its own permissions.

### Search everything you can open

You and your agents can search every doc you can open.

### Work across every agent and plan

Claude, ChatGPT or Cursor, on personal or company plans. One doc, one URL.

### Build internal apps (private beta)

Develop applications that pull data from your sources.

### Connect your data sources (private beta)

Pull data from the sources your team already uses.

## Questions about Claude Code artifacts and Display

### Why did Claude Code write a local HTML file and not publish an artifact?

Claude Code publishes an artifact only when you sign in with a claude.ai account. A session that uses an API key, a gateway token or a cloud-provider credential cannot publish. This includes Amazon Bedrock, Google Cloud and Microsoft Foundry. Publishing is also off by default in the Agent SDK, the GitHub Action, MCP-server contexts and claude -p. In these cases, Anthropic's documentation says that Claude writes a local HTML file or says it cannot publish. The terminal can also show the error “Artifacts need a claude.ai login”. From an API-key, gateway or cloud-provider session, you can publish that file to Display.

### Can I publish from Claude Code on Bedrock, Vertex AI or an API key?

Yes. Add the Display MCP endpoint to Claude Code and complete the browser sign-in. You can also connect with a Display API key or the dsp CLI. Display has its own sign-in, so it does not need a claude.ai account or a specific model provider.

### How much does Display cost?

The Free plan includes 3 pages behind sign-in, unlimited public pages and one-time password sign-in. Solo costs $9 a month billed yearly, or $12 monthly, and adds Google and Microsoft sign-in. Team costs $59 a month billed yearly, or $79 monthly, for the whole company. Viewers and commenters are free on every plan. For the cost of Claude seats for readers, see [the Claude Team sharing comparison](/claude-team-artifact-sharing-alternative).

### Who can open a page?

A new page is private by default. You can share it with people and groups, open it to everyone in your company, or make it public. People sign in with a one-time password before a private or company page opens. Solo and higher plans add Google and Microsoft sign-in. Enterprise adds SAML sign-in, for example with Okta.

### Is Display a second tool to manage?

It is one more connection for your agent. Add the Display MCP endpoint or the dsp CLI once, then ask the agent to publish. Many teams keep Claude Code artifacts for sessions that sign in with a claude.ai account and publish to Display for the others. Claude Code artifacts are built in and cost nothing more.

### Does Display use my content to train AI models?

No. We do not use customer content to train or fine-tune any AI or machine-learning model.

### Does Display work inside Claude Code?

Yes. Connect Display from Claude's connector directory or add the Display MCP endpoint, then ask Claude Code to publish the page. Claude Code returns a URL, and each update keeps the same URL.

### Can someone without a Claude account open a Claude Code artifact?

Yes, if the artifact has a public link. Anyone on the internet can open a public link without a claude.ai sign-in. On Claude Team and Enterprise, public links are off until an Owner turns on External sharing. Behind sign-in on Team and Enterprise, readers are members of your Claude organization. For people outside the organization, Anthropic's help center describes email invitations, which are in beta. Each invited person needs a Claude account. The Claude Code documentation does not list this option.

### Which agents work with Display?

Any agent that writes HTML or Markdown, for example Cursor, Codex, Claude Code, Claude and ChatGPT. Agents connect through the Display MCP server, the CLI or the API. Each person can use a different agent on the same page.

### How do I move a Claude Code artifact to Display?

Ask Claude Code to publish the HTML or Markdown file it wrote to Display. A page that calls Claude connectors does not get that data outside Claude.

### Is Display open source?

No. “Open” means three things. Any agent can publish to Display. Anyone you choose can open a page without a seat. You can download the source file of any page at any time.

### Our organization has Zero Data Retention. Can we use Display?

That depends on your own requirements, and we make no claim that Display meets them. Claude Code artifacts are not available to organizations with Zero Data Retention, HIPAA or customer-managed encryption keys. Display is a separate service with its own terms, and it stores the pages you publish. Check Display against your requirements before you publish.

### Can I mention an agent in a Display comment?

Not yet. Comments addressed to an agent are planned. Today, you ask your agent to read the comments. It replies, publishes the next version at the same URL and resolves the threads it answered. In Claude, a person who can edit the artifact can send a comment to Claude with @claude.

### Can a Display page pull live data through each viewer's connectors?

No. A Claude Code artifact can call MCP connectors with each viewer's own account, and Display does not offer this. Keep those pages in Claude.

## Publish the page from the session you already use

Add the Display MCP endpoint or the dsp CLI once. Then ask Cursor, Codex, Claude Code or any other agent to publish.

[Start free](https://app.display.dev/) · Free plan · No card required · Viewers and commenters are free