GUIDE · UPDATE AN EXISTING ARTIFACT

Change the HTML. Keep the link.

Keep revising with your agent. Your readers keep the same link.

How do you update HTML without changing its link?

To update an HTML page without changing its link, give your connected agent the existing share URL or page ID and describe your changes. It needs the complete source to prepare complete replacement HTML. Review the revision, then ask it to update that artifact—not publish a new one. Check the result and access settings at the same link.

Connect your agent See the four-step update

Last verified September 4, 2026 · update, sharing, and delivery contracts

BOUND ARTIFACT01 / CURRENT

REPLACEMENT HTMLREADY

A clearer answer now lives here.

ARTIFACT IDp_yK7mP2qR9vT4xN6cL8wB3A

SHARE URL · ATTACHED TO THIS ARTIFACThttps://shareartifacts.dev/view/p_yK7mP2qR9vT4xN6cL8wB3A

Feedback changes the document, not the address you already sent.

THE MENTAL MODEL · 01

Update the artifact, not the address.

Correct a finding, add a source, or improve the explanation with your agent. You do not need a separate editor or another link to send around. Updating replaces the complete document behind the address your audience already has.

EXISTING pageIdCOMPLETE HTMLSAME SHARE URL

The agent prepares the complete replacement from your source.

Replaced: The complete HTML and, if supplied, the title.
Unchanged: Page ID, share URL, access policy, expiration, and status.
Controlled separately: Who can open the artifact and whether it is online.

How the agent keeps the same link and verifies the update

ONE CHECKED CONTRACT · 02

The content changed. The address did not.

The share URL is built around the artifact's random page ID. update_page sends one complete replacement document to that existing ID. publish_html creates a different artifact and therefore a different URL. Our checked MCP lifecycle publishes an artifact, updates it, and asserts that the returned page ID and absolute public URL still match. The content hash changes because the document changed.

Before changing anything, call get_page and get_page_sharing; save its pageId, publicUrl, version, contentSha256, and sharing settings. After the update, confirm that pageId and publicUrl match the saved baseline and that version advanced. Compare contentSha256 when the sanitized HTML should differ, inspect the same URL, and use get_page_sharing to confirm access. If the response is uncertain, reconcile both reads before another update.

Before feedbackDraft

LAUNCH DECISION BRIEF

Before feedback: The decision, with its evidence attached.

Source note incomplete
Recommendation needs context

pageId: p_yK7mP2qR9vT4xN6cL8wB3A
publicUrl: https://shareartifacts.dev/view/p_yK7mP2qR9vT4xN6cL8wB3A
status: published
version: 7
contentSha256: 3c7a1d9e3c7a1d9e3c7a1d9e3c7a1d9e3c7a1d9e3c7a1d9e3c7a1d9e3c7a1d9e

update_pageCOMPLETE HTML REPLACEMENTSAME ID + URL

After feedbackReviewed

LAUNCH DECISION BRIEF

After feedback: The decision, with its evidence attached.

Source note added
Recommendation includes the caveat

pageId: p_yK7mP2qR9vT4xN6cL8wB3A
publicUrl: https://shareartifacts.dev/view/p_yK7mP2qR9vT4xN6cL8wB3A
status: published
version: 8
contentSha256: a84f2b61a84f2b61a84f2b61a84f2b61a84f2b61a84f2b61a84f2b61a84f2b61

Illustrative contract proof · synthetic fields, verified invariants. The matching labels make the unchanged values explicit.

AGENT WORKFLOW · 03

Turn feedback into a revision, in the same conversation.

Tell your agent what needs to change. Review the work before it replaces what your readers see.

Point to the work you shared
Give your connected agent the current share URL or page ID. If you only know the title, ask it to find the artifact and confirm the exact match before making changes.
Describe what should change
Explain the corrections, feedback, or new information in the conversation where you created the work. The agent needs the complete source HTML to prepare the replacement. If it no longer has that source, provide it before continuing; you do not need to hand-code the revisions.
Review and approve the revision
Review the complete revised document, not just the changed section. When it is ready, ask your agent to update the existing artifact, keep its access settings, and return the same link—not publish a new artifact.
Check the link your readers have
Open or refresh the existing link and check the result and who can access it. Your agent should verify that the update succeeded. If it reports an uncertain result, ask it to check the artifact before trying again.

A PRECISE UPDATE REQUEST

Describe the change. Keep the existing link.

Revise the existing artifact at [CURRENT SHARE URL]: [DESCRIBE MY CHANGES]. Use the complete source HTML from our conversation. If you do not have it, ask me for the source; do not reconstruct it from a rendered page or guess missing content. Show me the complete revision for approval before updating. Once I approve, update the existing artifact; do not publish a new one or change its access setting. Verify the update and return the same share URL.

CONTENT AND ACCESS ARE SEPARATE · 04

Keep the address. Control the rest.

Replacing HTML does not make a private, restricted, expired, or offline artifact public. Review access separately whenever the audience changes.

01 Content: update_page replaces the complete HTML and can change the title. The page ID and share URL stay the same.
02 Access: Owner-only, public, password, exact recipients, or an exact email domain remain separate choices; expiration remains separately set.
03 Availability: Its sharing policy, expiration, and published or offline state stay unchanged. Updating an offline artifact leaves it offline.

Update an artifact while it is offline

unpublish_page
Keeps the ID and URL, takes delivery offline, and revokes issued viewing tickets.
update_page
Replaces the HTML while the existing artifact remains offline.
publish_page
Brings that artifact back at the same URL. Old viewing tickets are not restored; recipients reopen the link and may need to unlock it again. Use get_page to confirm the current URL and state.

SAME ARTIFACT OR NEW ARTIFACT? · 05

Reuse the link only when it should keep the same meaning.

If someone who saved the old link should see the replacement, update the existing artifact.

If the old page should remain separately available, publish a new artifact.

KEEP THIS LINK

The deliverable still means the same thing.

Correct an error or add a missing source.
Respond to feedback on the current deliverable.
Refresh facts, language, or visual design.
Clarify the recommendation at this address.

CREATE A NEW LINK

The old and new result must both have a place.

Both results need to remain separately available.
The work belongs to another client or decision.
Two audiences need different content at the same time.
The artifact type or purpose has changed.

An update is a full-document replacement. Keep the source you may need later, inspect the complete result, and use a second artifact when two states must coexist.

SAFE STATIC ON EVERY PASS · 06

Each revision goes through the same safety checks.

Every complete replacement is sanitized again. Scripts, forms, embeds, event handlers, and refresh redirects are removed; CSP blocks active API connections. Publisher-selected HTTPS images and fonts may still load from their hosts.

ONE ADDRESS · THE CURRENT ANSWER

Keep the link your audience already has.

Connect your agent Learn how to share HTML