Skip to content

Update an artifact

Change published work while keeping its URL and access.

On this page

Update an artifact to publish a new version at the same URL. Its visibility and invited people carry forward unless you change them.

Ask your AI tool

Name the artifact and the change you want. Your agent finds the current version, applies the change, and returns the same artifact link.

Find the Display.dev artifact named Quarterly plan. Change its status from Draft to Approved, publish the update at the same URL, and return the link.

If someone else updated the artifact first, the agent should show you the newer version and reconcile the change before publishing.

Publish a new version from the dashboard

  1. Open Artifacts and select the artifact.
  2. Under Versions, select Publish new version.
  3. Choose the updated file.

The file must keep the artifact's format. Choose a .md file for a Markdown artifact or an .html file for an HTML artifact. Publish a new artifact if you want to change formats.

The new version becomes current at the existing URL. The Versions list lets you view or download an earlier retained version. If you need to restore one, select Rollback beside that version.

Use the command line

For one exact text change, first get the current version:

bash
dsp get-metadata <shortId>

Then publish the replacement:

bash
dsp edit <shortId> \
  --base-version <currentVersion> \
  --old "Draft" \
  --new "Approved"

To replace the complete file:

bash
dsp publish report.md --id <shortId> --base-version <currentVersion>

--base-version prevents you from overwriting a newer update. If the command reports a version conflict, inspect the current version, apply your change to it, and retry with that version number.

See CLI commands for exact-edit options and Plans and limits for version-retention limits.

Was this page helpful?