Used by top teams at
Your agent publishes. Your team and clients open the URL and comment. Your agent updates it, and the next version lands at the same URL.
An agent publishes the Mossvane onboarding prototype to display.dev. The owner shares the private URL with everyone at Mossvane and adds an outside reviewer, who signs in with a one-time password. Priya opens it, clicks through to step two and comments that most creators pick a theme later. The agent adds a “Skip for now” link and publishes v2 at the same URL.
Fix any line right where you read it.
A Q3 delivery report is open on display.dev, 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
Three moments when your team needs to open the work, not a screenshot of it.
Review example 01
Let teammates test the responsive flow before engineering commits to the build.
Open the example“Design is the silent ambassador of your brand.”
Saved from an articleReview example 02
Test the responsive page and catch the last important tweaks before launch.
Open the exampleNotes, images and links land in one private place and sort themselves.
“Less noise, more of what I actually wanted to remember.”
Review example 03
Agree on the numbers and their definitions before they reach the board deck.
Open the example“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.”
IT and AI Ops Manager, Kogan.comRead the Kogan storyDisplay has already replaced Notion for me.
Before Display, we were sharing artifacts in Slack. For HTML artifacts, this meant messy and often confusing screenshots. Display is a perfect elegant solution for us.Read the story
Most of what I send clients goes through Display – reports with sensitive data behind a password, landing page mockups and ideas, keyword research and strategy docs.
All three can publish what your agent made – publishing isn't collaborating. Gating, comments, in-line editing, versions and an audit log decide whether your team can work in the artifact, and who else can see it.
Claude Artifacts
Codex SitesEvery version, comment and view is on the record, with the person or agent behind it.
Pin any version, review the history, never chase a v2 link again.
Versions and comments name who published them, in the thread and the audit log.
Everything your agent publishes lives behind your company's SSO. The right teammates are one click in. Everyone else sees nothing.
Shared with everyone at acme.com
Eligible new organizations start with seven days of Pro. No card required.
Try it. No credit card.
Individuals. Unlimited gated sharing.
For teams who need SSO & audit logs.
Any agent, any model. Behind your company's login, one flat price.
Free to start · Unlimited viewers · HTML or Markdown file to authenticated URL in 15 seconds