Quiver
Back to the changelog
Tessa Kriesel

Artifacts keep every version, and you can restore one

Editing an artifact used to overwrite it for good. Every edit now saves the version it replaced, and you can put any of them back.

Artifacts
Version history

Editing an artifact used to overwrite it for good. Every edit now saves the version it replaced, and you can put any of them back.

  • The artifact page lists its history newest first, with who made each change and whether it came from the app or from an agent.
  • Restoring keeps the artifact's ID and its status, so the campaign, the published content and the reminder to log results all stay attached to it.
  • A restore is saved as a version too, so restoring the wrong one is undone the same way.
  • Only a change to the title or the content saves a version. Retagging an artifact or moving it between campaigns does not.
  • Editing an artifact from your agent now edits it in place. It used to create a second artifact with a new ID, which left the original's reminder and anything published from it pointing at a copy that no longer changed.

Built with Quiver

This entry was drafted from merged pull requests.

Your agent turns shipped work into a draft changelog entry through MCP. You review it, publish it, and it appears on your own site.