A URL for everything Claude Code makes
Where humans and Claude Code
work on dashboards together.
Claude creates the artifact. display.dev is where your company sees it – one command, its own URL, and no Claude seat for viewers. It works with any agent, so switch to Codex or Cursor later and everything you published stays exactly where it is.
The demo shows an agent publishing a doc to display.dev – from a chat or a terminal – 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.
Cursor, Codex, Claude Code – any agent that writes a file. Switch agents anytime – your URLs, versions and comments stay put.
Used by top teams at
Share Claude Code work from a personal Max plan with your company
Many engineers pay for a personal Max plan to get higher Claude Code limits. The rest of the company is on Claude Team or Enterprise. Claude keeps these accounts separate. display.dev does not check the Claude plan.
| Task | In Claude | In display.dev |
|---|---|---|
| Share from a personal Max plan with your company's Team or Enterprise org | Invite each person by email, in beta | Choose Company. Everyone at your company opens it |
| Share from an Enterprise org with an engineer on Max | 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 |
| Ask the AI in a comment | Not for people invited from outside the org | Each person's own agent reads the comments |
Publish from Claude Code with the CLI or the MCP server. Neither needs a Claude organization. Colleagues comment on the artifact, edit it in the browser, or ask their own Claude to publish the next version. Claude's rules checked on 16 October 2026 against Anthropic's Share artifacts guide.
Why Claude Code output gets stuck locally
Claude Code writes self-contained HTML to disk: architecture proposals, competitive analyses, visual reports, interactive presentations. All beautifully rendered, all stuck on your machine. Claude Code Artifacts turn session work into an interactive 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.
The artifact took 60 seconds to generate. display.dev opens it to everyone at your company, with no Claude seat, and comments from your team feed straight back to the agent.
- ✗ScreenshotCharts, tabs and animations all flatten into a picture.
- ✗Claude shareEvery reader needs a Claude account, and an Enterprise org blocks outside invitations by default.
- ✗GitHub PagesYour PM, your exec and your client have no GitHub account.
- ✗Vercel plus sign-inA project, a deploy and protection settings before anyone reads it. Identity-provider sign-in is an Enterprise feature.
Three steps. Fifteen seconds.
Who can open it
A public URL for a demo or a client. Nothing to sign in to, no Claude seat.
Named email addresses only. Useful for a client or a contractor you don't want to hand company sign-in to.
Anyone signing in with a verified company domain gets in – Google Workspace, Microsoft Entra ID, or a one-time password by email. One time, five seconds, and viewers are unlimited and free.
You change the level any time. Move an artifact from company-gated to public and back. The URL stays the same.
Or: say it in Claude
Configure the display.dev MCP server once. After that, in any Claude conversation:
"Publish this architecture proposal to my team."
Claude invokes the publish tool, gets back a company-gated URL, and returns it in the conversation. No terminal. Works in Claude Desktop, Claude Code (with MCP), and any Claude-compatible client.
// Claude Desktop config (Settings → MCP Servers)
{
"mcpServers": {
"display-dev": {
"url": "https://api.display.dev/v1/mcp",
"headers": {
"Authorization": "Bearer sk_live_..."
}
}
}
}Or paste https://api.display.dev/v1/mcp into Claude's "Add custom connector" field and sign in with your work email – no key to manage.
Everything Claude Code generates
- Architecture diagrams
- D3, Mermaid or custom SVG, rendered as the page Claude wrote.
- Competitive analyses
- Sortable tables and interactive filters, still sortable and still interactive.
- Visual reports
- Charts, animated transitions and data grids.
- Interactive presentations
- Tabs, slides and dynamic content in one link.
- Dashboards
- Rich layouts with the data Claude assembled.
- Technical specs
- Long documents rendered as polished HTML instead of a file attachment.
Claude Code sharing options compared
| Option | Non-engineer viewers | Company auth | Interactivity | Time | Cost |
|---|---|---|---|---|---|
| Screenshot | ✅ (degraded) | – | ❌ | 10 sec | $0 |
| Claude org share | ❌ (needs seats) | ✅ | ✅ | 5 sec | $25+/seat/mo |
| GitHub Pages | ❌ | ❌ / $2,100/mo | ✅ | 5–30 min | $0 / $2,100/mo |
| Vercel + sign-in | ❌ | ✅ | ✅ | Longer, more steps | Pro per seat, and IdP sign-in needs Enterprise |
| display.dev | ✅ | ✅ | ✅ | 15 sec | €49/mo flat |
Pricing
Try it. No credit card.
- Included: 3 gated artifacts
- Included: Unlimited public artifacts*
- Included: 50MB storage
- Not included: Version history
- Not included: Google + Microsoft SSO
- Not included: Audit logs
display.dev branded
Individuals. Unlimited gated sharing.
- Included: Unlimited gated artifacts
- Included: Unlimited public artifacts
- Included: 1GB storage
- Included: 10 versions
- Not included: Google + Microsoft SSO
- Not included: Audit logs
For teams who need SSO & audit logs.
- Included: Unlimited gated artifacts
- Included: Unlimited public artifacts
- Included: 25GB storage
- Included: 50 versions
- Included: Google + Microsoft SSO
- Included: 90 days audit logs
For compliance-driven organizations.
From €499/mo
- Included: Unlimited gated artifacts
- Included: Unlimited public artifacts
- Included: Custom storage
- Included: Unlimited versions
- Included: Google + Microsoft SSO
- Included: 365 days audit logs
The free tier covers individual use with email OTP. Pro adds one-click Google and Microsoft SSO once the team is on board.
Features
Viewers click a link and sign in with their Google or Microsoft account, or a one-time password. No app to install. No account to create. No IT ticket.
Inline comments on every artifact. Your agent reads them via MCP, fetches the current version, republishes with short_id and base_version, and resolves the thread. For a small fix, your team selects Edit and changes the page directly. Every change lands at the same URL.
Ask your agent to publish the file to Display, in your terminal or in Claude Desktop. No git repo, no deploy pipeline, no project to configure.
Every artifact gets a URL that keeps working. Share in Slack, link in Notion, paste in email. It still works six months later.
No per-seat pricing at any tier. Share with your PM, exec, legal team, or designer for the same flat price.
Cursor, Codex, and Claude Code all work, plus any agent that creates HTML or Markdown output.
What teams say
We use it to share and collaborate on markdown and HTML artifacts, and it's helped us work together more seamlessly in this weird new agentic coding era. Our whole 7-person team uses it.Read the story
Try it free
- Publish a Claude Code artifact in under a minute, no card
- Keep the URL when you upgrade
- Unlimited viewers on every plan
Common questions.
Do my teammates need Claude accounts to view the artifact?
No. display.dev authentication is based on your company's Google or Microsoft email – the same account they use for everything else. No Claude subscription required for viewers.
I use a personal Max plan. Can my company on Claude Team or Enterprise work on my artifacts?
Yes. Publish from Claude Code with the CLI or the MCP server. Neither needs a Claude organization. Colleagues open the artifact with their work email and comment on it. Their own Claude can publish the next version at the same URL. On Team and Enterprise, an Owner adds display.dev from Claude's connector directory first.
Does this work with Claude Code CLI, not just Claude's web UI?
Yes. Claude Code writes HTML to disk. Ask it to publish the file to Display, regardless of which tool generated it.
What if my Claude Code output is several files, not a single HTML file?
Ask Claude Code to inline the CSS, JS and images into one self-contained HTML file, then publish that file. A single self-contained HTML file is the safe shape.
Can I update a published artifact?
Yes. Ask Claude Code to publish the new version to the same link. The link does not change – everyone who bookmarked or shared it sees the updated version.
Does the MCP version work from Claude Code CLI?
display.dev's MCP server works in any Claude-compatible MCP client. Claude Code's CLI supports MCP. Configure it in your ~/.claude/settings.json the same way you'd configure any MCP tool.
What about Claude Desktop artifacts specifically?
See /share-claude-artifact – same product, framed for Claude Desktop and the web app, including the inline comments your agent reads back via MCP.
Is my agent's work attributed to me?
Yes. When Claude Code publishes through display.dev it is recorded as "claude-code on behalf of you", in the comment thread and the audit log. See how identity works.
Publish your first artifact in 15 seconds.
Free tier. No credit card. One-time password auth on free, Google + Microsoft SSO on Pro (€49/month flat).