Which Artifact Edition Did You Review? Connecting Versions and Stored Files

Two people can call a document “the latest” while reading different content. This guide is for people who review and hand off documents made by an Agent in a ClawPod Cloud Room. You need access to the Room and a response delivered as an artifact; by the end, you will know how to distinguish the version you reviewed from the file you downloaded. An artifact is a versioned result generated in a conversation, and a version identifies a particular edition of that result.

Record the reviewed edition, not just “the latest”

• The official Guide describes opening the exact version from an artifact card and selecting a version when several exist.
• Downloads are .html for HTML artifacts and .md for other artifacts. This does not mean automatic conversion to PDF or Office formats.
• Connect the reviewed edition, downloaded file, and approval decision in your team records. Artifacts do not automatically synchronize with Agent workspace files.

The interaction descriptions here stay within the official Guide. They do not assume button locations or editing menus in your current interface.

Open the card, then check the content

A Room is a shared conversation space for users and Agents. Sending a message does not mean the work is complete. First check for a response or processing state from the intended Agent.

According to the Guide, selecting an artifact card on a message opens the Artifact panel, a separate view of the result. The panel loads that artifact’s exact version. When several versions exist, you can select one, and you can preview Markdown and HTML content. Markdown is a document format that uses symbols for elements such as headings and lists.

Cards are provided only when the Agent responds in artifact form. If the response is an ordinary message, do not proceed as if a card exists. You can ask, “Check whether you can provide this result as an artifact; if not, explain an alternative.” The request itself does not guarantee a card.

Selecting a version does not replace content review. Read the body to confirm the requested change, even when the title is unchanged. The Guide does not describe a direct editing menu, editing permissions, a rule that every revision creates a new version, or a restore-previous-version feature. When a change is needed, tell the Agent what to change and what to retain, then inspect the returned result. Do not assume it will arrive as a new version of the same card.

Example: correct a meeting summary before handing it off

This is an illustrative example. Document names and version labels are explanatory, not a real interface or execution record. Assume the supplied notes say, “Materials owner: Minji; deadline: Friday.”

The reader’s request

Using only the supplied meeting notes, check whether you can create “Weekly meeting summary” as a Markdown artifact. Include decisions, owners, and deadlines, and ask about unclear details. Do not overwrite existing files or send anything externally. When finished, provide the result and explain what you checked.

Illustrative result and correction request

The first result arrives as an artifact. The reader opens version 1, which says, “Materials owner: Junho; deadline: Friday.” Comparing it with the source notes reveals the error. The reader asks:

Correct the materials owner to Minji, as stated in the notes. Keep the Friday deadline and the other decisions unchanged. Provide the revised result and explain what changed. Do not share it externally.

For this example, assume the revision arrives as version 2 of the same artifact. This is not a promise about every revision request. The Agent’s illustrative response says, “I changed the owner to Minji and kept the Friday deadline. Nothing was sent externally.” Rather than relying only on that response, the reader opens the actual result.

Check	Illustrative observation	Decision
Selected result	Weekly meeting summary, version 2	Edition under review
Source and body	Owner Minji, deadline Friday	Matches the notes
Downloaded file	weekly-summary-v2.md has the same owner and deadline	File content also matches
Sharing status	Review complete; external sharing not approved	Do not send before approval

The filename is an example chosen by the reader when storing the file, not an automatic naming rule. “Review complete” and “sharing not approved” are team records, not descriptions of product approval indicators.

Verify success by checking that the selected edition, its body, and the downloaded file all contain the same correction. Then record something like “Weekly meeting summary / reviewed version 2 / stored file weekly-summary-v2.md / owner correction checked / sharing approval pending.” Before storing the file in an organization repository, confirm the permitted location and access scope.

If verification fails, do not mark the task complete. If version 2 will not open, use the error distinction below to check access or the target version. If the file still names Junho, compare the selected edition with the downloaded content and hold the incorrect file from circulation. If the revision arrives as a separate card or an ordinary message, identify the result actually received; do not assign the old card’s version number to the new result.

A download starts preservation, not format conversion

The Guide describes copying Markdown or plain text to the clipboard. For file downloads, use these boundaries.

Result	Download format in the Guide	Before handing it off
HTML artifact	.html	Check the recipient’s viewing method and security procedure
Other artifact	.md	Check the content and whether the recipient can use Markdown

Previewing an HTML artifact is different from attaching an HTML file to chat. According to the Guide, HTML attachments are downloaded; execution and preview inside chat are not provided. Downloading an artifact and attaching it again does not preserve the same viewing experience by implication.

If you need PDF, DOCX, or another format, first check that the Agent environment has a tool capable of generating it. Accepting a format for upload does not guarantee the Agent can produce it. Changing an extension is not file conversion either.

Report the specific error when a result will not open

The official Guide describes forbidden when access is not permitted and not found when the requested version does not exist. Do not interpret both as “the document disappeared.”

• forbidden: ask the responsible person to check the account in use and its Room and organization access scope. Organization permissions affect Room access, but this error alone does not identify the responsible permission setting. Do not send the file through another route to bypass an access restriction.
• not found: check the intended artifact and version with the author. This message alone does not establish deletion, retention expiry, or recoverability. If you have a previously stored copy, identify it as a separate copy rather than presenting it as the latest result.

Report the error text and the result you tried to open without copying sensitive body content or secret values. Do not treat resending links or changing permissions as automatic fixes. Establish the cause, then choose an authorized action.

Reading, editing, sharing, and preservation are different decisions

Being able to open a result does not establish permission to edit it or share it externally. The collaboration Guide says to check who can read the file in the Room or organization, which workspace or Task it connects to, and the applicable retention, deletion, and download policies before sharing. Check for personal information, customer data, and secrets as well. A preview is not a security scan or complete file validation.

Artifacts and Agent workspace files do not synchronize automatically. Do not expect editing a downloaded copy to change the Room result, or changing a workspace file to update the card. Store important files in an organization-approved repository and record which result was reviewed. This is a team preservation procedure, not a description of automatic export.

The public documentation did not confirm version-count or retention limits, side-by-side comparison, restoration of an earlier version, or automatic export to an organization repository. If these are requirements for your work, confirm them separately before relying on them. Deleting a Room can affect access to its history, so preserve required outputs and decisions and check connected automation before tidying it up.

For your next document, replace “the latest” with the reviewed result and version, the stored file, and sharing approval status. The next reader then has a concrete reference for checking that you are looking at the same content.

Sources

• ClawPod Guide — File Formats and Agent Artifacts: cards and versions, copying and downloading, errors, and separation from workspace files.
• ClawPod Guide — Collaborating with an Agent in a Chat Room: requests and completion checks, preserving outputs, Room access and deletion cautions.
• ClawPod Guide — Chat and Collaboration: access scope, retention and download policies, and sensitive-data checks before sharing.