Prototypes and design explorations
Clickable HTML anyone can open, no repo and no local server. Your PM and designer click through the real thing in the browser. No GitHub account required.
Open a live prototypeClaude publishes the artifact. Your team needs no Claude seat and opens it with the Google or Microsoft account they already use.
The demo shows an agent publishing a doc to Display from a chat, then a teammate opening its URL, selecting Edit, changing a number on the page and saving v2, a colleague commenting on v2, the agent publishing v3 at the same URL and resolving the comment, and the doc being shared with someone outside the company.
Used by top teams at


Many developers and designers pay for a personal Max plan to get higher usage limits. The rest of the company is on Claude Team or Enterprise. Claude keeps these accounts separate. On Display, everyone signs in to your company's organization with their work email, so the Claude plan does not matter.
| Task | In Claude | In Display |
|---|---|---|
| Share from a personal Max plan with your company's Team org | Invite each person by email, in beta | Choose Company. Everyone at your company opens it |
| Share from an Enterprise org with a colleague on Max or Team | Outside invitations are off by default | Same organization. Nothing to turn on |
| Open an artifact that someone shared with you | You need a Claude account | Your work email. No Claude account |
| Share a Claude Doc outside a Team or Enterprise org | Not available | Any HTML or Markdown file |
| Ask the AI in a comment | Not for people invited from outside the org | Each person's own agent reads the comments |
Any member can comment on a Company doc, and people with edit access select Edit and change it on the page. Each member can also ask their own Claude to publish the next version at the same URL. On Team and Enterprise, an Owner adds Display from Claude's connector directory first. Claude Code connects on any plan. Claude's rules checked on 16 October 2026 against Anthropic's Share artifacts guide.
Claude's built-in publish gives you a claude.ai/public/artifacts/… URL. Fine for a public demo. Claude Code Artifacts add a private page on claude.ai. Every person you invite needs a Claude account, Enterprise turns off invitations outside the organization by default, and the source has to be Claude.
A public URL is the only way to show the page to someone without a Claude account.
A reader without a Claude account cannot comment, so notes land somewhere the agent can't read.
Six months later the context is gone and so is the artifact.
Nothing to organize, no address of your own.
One more thing for your security team to say no to.
Display opens viewing to anyone with their company sign-in and no Claude seat, and adds comments and updates from any agent. Spaces and folders organize your artifacts, search finds them, and they outlive the chat window.
“Publish report.html to Display.”The URL comes back in the same turn.
“publish this to Display”Add Display as an MCP server and ask in plain English. One sentence, no copy-paste.
Download the artifact's HTML from claude.ai and publish it in app.display.dev. Pick who can open it, get the URL.
"Publish ./artifact.html to Display."
Your agent returns a link, for example https://acme.dsp.so/0kzNYG7O-revenue-dashboard.
The agent publishes the file and returns the URL. What opens is the artifact itself – JavaScript, charts, filters, hover states – not a screenshot of it.
To change it later, ask your agent to publish the next version. Same URL, new version, comments and history intact.
Every new doc starts private. Share it with people and groups, and invite clients or partners by email with a role: Viewer, Commenter, Contributor or Editor.
Open a doc to your whole organization. On Solo and higher plans, colleagues sign in with the Google or Microsoft account they already use.
Make a doc public when anyone should open it, with no sign-in.
On Team and Business, see who opened each doc, and when.
Anything Claude can write, your team can open in a browser. Six artifacts published from real agent runs – every one of them live right now.
Clickable HTML anyone can open, no repo and no local server. Your PM and designer click through the real thing in the browser. No GitHub account required.
Open a live prototypeRendered exactly as Claude built them, filters and hovers intact. Full JavaScript, CSS and D3. What the artifact does on your screen is what your team sees.
Open a live dashboardOne URL that always shows the current version. A comment lands, Claude updates the artifact, the same URL shows v2. The version history shows who published each version, human or agent.
Open the PRD exampleCI output your whole team can actually open. Playwright runs, coverage and logs, published straight from the pipeline – no repo access needed to read them.
Open a live test reportGated to your org, with an audit trail. Versioned, private by default, and on Team and Business you see who opened it, and when.
Open a live postmortemCharts stay interactive instead of flattened into a screenshot. Claude publishes the review as a real page: filters, hovers and drill-downs keep working for everyone who signs in.
Open a live growth review| Method | Its own URL | Company auth | Invited people | Inline comments | Custom domain |
|---|---|---|---|---|---|
| Anthropic publish | Yes(on claude.ai) | No | No | No | No |
| ShareMyArtifact | Yes | No | No | No | No |
| ShareDuo | Yes | No | No | No | No |
| OneClickLive | Yes | No | No | No | No |
| Tiiny Host | Yes | No | No | No | Pro |
| Yes | Yes | Yes | Yes(read via MCP) | Your name on dsp.so |
The other tools stop at "the link works." Display is built for what happens after that: humans leave feedback, the agent reads it back and republishes.
Claude publishes, your team comments, then Claude publishes the next version at the same URL.
Fix any line right where you read it.
A Q3 delivery report is open on Display, with 89.7% in its On-time rate tile. Someone selects Edit in the header, changes the tile to 94.4% on the page, and selects Save changes. The report reopens as version 4 at the same URL.
Shows this step in the loop
Free covers 3 gated docs, unlimited public docs and unlimited viewers. That is enough to try comments and new versions with your team before you pay.
$9/mo · $108 billed yearly
Includes
$59/mo · $708 billed yearly
Everything in Solo, plus
$199/mo · $2,388 billed yearly
Everything in Team, plus
$0
Includes 1 Editor or Contributor · 3 gated documents · 50 MB storage · Random subdomain
Get startedA PM highlights a paragraph and leaves a note. Claude reads the thread over MCP, publishes the next version at the same URL, then resolves the thread. For a small fix, people with edit access select Edit and change the page directly.
Google Workspace and Microsoft Entra ID on Solo and higher plans, or a one-time password by email on every plan. No new accounts for viewers, no per-viewer license.
Every republish adds a version to the same link. Viewers always get the latest; earlier versions stay one click away on the version pill.
Claude Code today, Codex or Cursor tomorrow. The URLs, versions and comments stay where they are.
Interactive charts, custom CSS, embedded data. If Claude can write it, Display serves it.
Spaces and folders organize what your team publishes. You and your agents can search every doc you can open.
Team and Business show who opened each doc, and when. Business adds 365 days of audit logs.
“It's helped us delay a switch to Anthropic enterprise plans, which we probably would've been forced into so we could collaborate on Claude Design output.”
Invite people by email and give each one a role.
Each publish and each edit saves a version. The link stays the same.
Spaces and folders for each team and each client.
You and your agents search every doc you can open.
Each doc shows who opened it, and when.
Private betaInternal apps that get data from your sourcesConnectors for the tools your team uses
Add Display once. Then ask your agent to publish.
Publish a Claude artifact in under a minute, no card · Keep the URL when you upgrade · Unlimited viewers on every plan
All three. Claude Code and Claude Desktop publish through the Display MCP server. For an artifact or Claude Design prototype built in the claude.ai web app, export its standalone HTML file and publish it in app.display.dev. In three exports we verified, the interactions we exercised still worked after publishing: a screen change, FAQ expansion and search filtering.
A new doc 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 Google, Microsoft or a one-time password before a private or company doc opens. Enterprise adds SAML sign-in, for example with Okta.
Teammates comment on any line of the page. People with edit access select Edit and change the doc right on the page. Your agent reads the doc and its comments, publishes the next version at the same URL, and resolves the threads it answered. Each save or publish adds a new version. On Solo and higher plans, you can open and restore earlier versions.
Yes. Invite them by email to a doc or a folder, and give them a role: Viewer, Commenter, Contributor or Editor. They sign in with a one-time password, Google or Microsoft. They do not join your organization.
Yes. Display does not check anyone's AI plan. Everyone signs in to your Display organization with their work email, whether their agent runs on Claude Pro, Max, Team or Enterprise. They all publish to and open the same docs.
Any agent that writes HTML or Markdown, for example Claude, Claude Code, ChatGPT, Codex and Cursor. Agents connect through the Display MCP server, the CLI or the API. Each person can use a different agent on the same doc.
HTML and Markdown files open as pages: reports, dashboards, specs, prototypes and slides. Folders also store other files, for example images, PDFs and data files, so people and agents find everything in one place.
Yes, for the docs that your team and your agents write: specs, plans, reports and wikis. Spaces and folders organize them, search finds them, and people comment and edit right on the page. To move existing pages, export them from Notion or Confluence as HTML or Markdown, and ask your agent to publish them.
Yes. On Solo and higher plans, every doc shows its view count. Team and Business also show who opened each doc, and when.
Yes. An Owner adds the domains of those services to the domain allowlist in Settings. Your published HTML pages can then get data from those domains and send data to them, for example from a form to a webhook. The other service must also accept the request. Display does not add a login or an API key, so keep secrets out of the page. The Business plan includes the domain allowlist.
No. We do not use customer content to train or fine-tune any AI or machine-learning model.