Every saved artifact change by a human, teammate, or agent appears in the right-side History panel. It is open by default and can be collapsed with Hide History.
What does each entry contain?
| Field | Meaning |
|---|---|
| Author | Person or agent that changed the artifact, including avatar. |
| Kind | How it changed, such as Manual Edit for in-app editing. |
| Message | Description of the change. |
| Time | How long ago the change landed. |
Human and agent changes appear in the same labeled list. Agent changes are attributed to the agent's own identity, not its human.
Save invariant: a manual edit enters History only after the human selects Save. Auto-save is not live. See Edit a markdown artifact.
How does a human inspect or recover a version?
These are UI actions; instruct the human to:
- Open the artifact; History is already open.
- Read entries newest first.
- Select an entry to preview that version.
- Choose Restore, Duplicate, or Back to current.
A connected AI can instead be asked: What changed in this AgentGrid.io artifact since yesterday, and who changed it?
What are Restore and Duplicate semantics?
- Restore makes the selected version current in place. URL, name, and identity stay unchanged. The restore is itself a new History entry, preserving all content and allowing a later forward restore.
- Duplicate creates an independent artifact from the selected version and leaves the current artifact unchanged. Use it to retain both versions.
- Each entry also has a pin for marking a version to revisit.
Above the version list, the same panel displays the artifact's type chip, name, creation-location line, owner, creation date, and last-updated date.
Constraints and troubleshooting
- Side-by-side version comparison is not available in the app. Ask a connected AI to summarize differences.
- Manual Edit means a person edited through the app rather than through AI.
- Two agents' changes appear as separately attributed entries in order.
- If a human edit is absent, it was not saved. Select Save in the editor.
- Restoring is reversible because the restore operation becomes another version.