[Feature Request] Artifact version history retrieval and URL versioning support
Bug Description
Hi guys, great product, I am using every-day-bases, thank you. Would be great to be able to fetch for older artifact versions, i am stuck in the last version from the prompt, the url is the same even if i select to share the artifact by versioning in the UI. So if the agent update the artifact version I just loose access to the last versions information.
Environment Info
- Platform: linux
- Terminal: vscode
- Version: 2.1.216
- Feedback ID: c7b9487f-4155-4a97-806a-c92a0e78d2f6
Agent Response
I don't have a tool to enumerate an artifact's version history — Artifact with action: "list" only lists distinct artifacts (one row each, current state), and WebFetch only returns the current published content. There's no version-history endpoint exposed to me.
The version picker you'd see in the claude.ai UI (mentioned via the label field when publishing) isn't something I can query — that's client-side only. If you need to compare against an older version, you'd have to pull it up in the browser yourself and paste me the content, or tell me what changed and I can help from there.
3 Comments
This would be very useful - when design changes are made it would be good to distinguish
Adding a concrete example of why this matters: I edit Claude Artifacts freely because I assume I can recover a previous version if something goes wrong.
Today, a document I’d spent hours refining (https://claude.ai/artifact/M828QR4bYwxmVe287CspiF?sk=qHwgDmQQkqHbpB2PK7IlxQ) was completely overwritten with a version from weeks ago. I haven’t found a way to recover the pre-overwrite content.
I can move important docs into our team wiki, but being able to recover earlier versions feels like a basic requirement for trusting Artifacts with substantive work.
This changes how comfortable I am iterating in Artifacts. If a bad edit can cost me hours of work with no apparent way back, I have to start treating every edit as a potential loss.
@bcherny Is there a recovery path I’m missing? And can we get reliable version history that both users and agents can retrieve and restore?
Also cc @Cammac7
I do report identical issues and consequences as stated by @danielglasgow