Artifact versions

Open in product: preshos.com/agent-ops/artifact-versions

Artifacts iterate in the Workspace. Each round of agent work produces a new version of the output while earlier versions stay on the record. Versions are identified by content hash: identical content means the identical version, so the history shows exactly what changed and when. Versions exist so review moves forward — the latest is what gets decided on — without losing what came before.

Version discipline

• Review the latest version. Earlier versions are context for how the output moved, not alternatives to pick between silently.
• Each version answers the last round of feedback. If a new version ignores review notes without saying why, stop and ask before approving.
• The version history is part of the session record. What was attempted, approved or denied, and changed stays attached to the versions it produced.

Requesting changes

• One round of feedback at a time, aimed at the latest version. Scattered notes across old versions produce merged confusion.
• Say what is wrong and what good looks like. “Tighter” is a mood; “cut the second section, keep the table” is an instruction.
• Big direction changes may deserve a fresh session rather than version twenty of a thread that started somewhere else.

What next

• Working folder vs artifacts: which outputs get versioned.
• Sessions: the preview surface versions render in.
• Approving agent actions: deciding on the version in front of you.