---
title: Publish with your agent
description: Ask your AI tool to publish its work, choose who can open it, and keep updating the same link.
slug: /docs/publish-with-agent
group: publish
updatedAt: 2026-10-05
---

Ask your connected AI tool to publish what it made and get back a link you can share. Each published page is an **artifact**: an HTML or Markdown page with its own URL. Your agent can update it later, and the link stays the same.

Connect your AI tool first. See [Quickstart](/docs#connect-your-ai-tool).

## Ask your agent to publish

Tell the agent what to publish and who should open it. To publish work from the current conversation:

> `Publish this with Display.dev as Company so everyone in my organization can open it. Name it Quarterly plan and return the link.`

To have the agent make the page first:

> `Create a self-contained HTML status report of the project in this directory: what it is, what changed recently, and what is in progress. Publish it with Display.dev as Company and return the link.`

The agent returns the artifact's link, for example `https://<org>.dsp.so/abc123-quarterly-plan`. Open it to check the result. Sign in if asked.

If you do not give a name, the agent chooses one from the file or the request. You can ask the agent to rename it later.

## Choose who can open it

Your agent publishes as **Private** unless you ask for another audience. Name the audience in your request:

| Ask for                                   | Who can open it                                                                                                                     |
| ----------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------- |
| Private, or say nothing                   | Only you, until you invite someone.                                                                                                 |
| Company                                   | Members of your organization, after they sign in.                                                                                   |
| Private and the email addresses to invite | You and the people you invite. People outside your organization sign in with a one-time password (OTP) sent to their email address. |
| Public                                    | Anyone with the link. No sign-in.                                                                                                   |

Company and Private artifacts count toward your plan's gated-artifact limit. See [Plans and limits](/docs/limits).

An Owner can turn off Public artifacts or sharing outside the organization. If your request needs a setting that is off, Display.dev refuses the publish and the agent tells you why. Choose another audience, or ask an Owner to change the setting. See [Organization artifact access](/docs/artifact-access).

To change the audience later, ask the agent or open the artifact in the dashboard. See [Sharing and access](/docs/visibility).

## Update the same artifact

To change published work, ask for an update and name the artifact. The agent publishes the next version at the same URL, so the link you already shared shows the change.

> `Update the Display.dev artifact named Quarterly plan. Add a Risks section after the summary, publish the update at the same URL, and return the link.`

If you ask the agent to publish again without naming the existing artifact, it can create a second artifact with a new link.

To change one line yourself, open the artifact and select **Edit**. See [Update an artifact](/docs/update-artifact) and [Edit an artifact in your browser](/docs/edit-artifacts).

## Act on comments

Members of your organization who can open the artifact can select a passage and comment on it. Invited people outside your organization can open the artifact but cannot comment.

Ask your agent to address the open discussions:

> `Review the open discussions on the Display.dev artifact named Quarterly plan. Make the requested changes when they are clear, publish the update at the same URL, reply with what changed, and resolve only the discussions you addressed. List anything that needs my decision.`

See [Review comments](/docs/comments).

## What you can publish

- **One HTML or Markdown file per artifact.** HTML can include its own CSS, JavaScript, and embedded images. Ask for a self-contained HTML file so the page does not depend on files the agent did not publish.
- **Data from other sites.** The page can exchange data only with sites on your organization's [domain allowlist](/docs/domain-allowlist). An Owner manages the list. Images, scripts, styles, and fonts from other HTTPS sites load without an entry.
- **File size.** Each plan has an upload limit per artifact. See [Plans and limits](/docs/limits).
- **Format.** An update keeps the artifact's format. To change from Markdown to HTML, publish a new artifact.
- **Claude Cowork on a personal Pro or Max plan.** The agent can publish pages it writes in the conversation. It cannot transfer large existing files. See [Claude Cowork](/docs/mcp-claude-cowork).

## If the agent is not signed in

An agent that is not signed in to Display.dev can still publish, but only as a public preview. Anyone with the preview link can open it. The agent also returns a single-use claim link.

Open the claim link and sign in to move the artifact into your organization. It stays Public until you change who can open it. See [Publish without an account](/docs/claimable).

## If your AI tool cannot connect

Ask the AI tool for the complete file, save it, then publish it from your browser.

> `Create a self-contained HTML status report of what my team is working on now: goals, recent progress, and next steps. Return the complete HTML file so I can save it.`

See [Publish from your browser](/docs/web-upload).
