Version history

History records artifact changes with their author, change kind, message, and time. Human, agent, Canvas, branch, and restore activity appears in the same timeline. A branch is a separate line of changes that can later be merged into the main artifact.

Read, preview, and compare

Open the History panel and select an entry to preview that revision without changing the current artifact. Use Compare to compare the selected revision with latest. Historical previews are read-only; return to current before editing or publishing.

Branch previews

Branch work appears in History as branch commits. A branch can be opened through its branch URL using ?branch=<name>. Branch previews are read-only in AgentGrid.io. Complete the merge in the workflow that created the branch, then return to the main artifact and verify the merged revision in History.

Do not publish or restore from a branch preview. A branch link follows a named branch; a pinned revision link identifies one fixed revision.

Restore, duplicate, and pin

• Restore makes the selected revision current on the same artifact. The restore creates a new History entry, so it is reversible.
• Duplicate creates a new independent artifact from that revision. It does not replace current state.
• Pin marks a revision for quick return. It does not change current content, move the artifact, or create a branch.

Checkpoints and recovery

Markdown changes autosave continuously. Save or ⌘S creates a checkpoint, which is a named entry in History. If a concurrent edit or Canvas save produced the wrong result, compare the relevant revision with latest before restoring.

A connected agent can summarize differences or inspect attribution. For branch work, give it the exact branch name or URL; do not let it infer one.

Related: Edit markdown · Canvas · Rename and duplicate

Questions and answers

Does previewing or comparing a revision change the artifact? No. Historical previews and Compare are read-only.

Is Restore destructive? No. It makes the selected revision current and adds a new History entry, so the restore itself can be reversed.

When should I use Duplicate instead of Restore? Duplicate when you want an independent artifact from the old revision; Restore when the original artifact should return to that content.

Can I publish a branch preview? No. Merge it in the workflow that created the branch, then verify the main artifact before publishing.

Direct answer

History is the attributed timeline for human, agent, Canvas, branch, and restore changes. A branch is a separate line of changes that can later be merged into the main artifact. Each entry includes author, change kind, message, and time. Selecting an entry opens a read-only historical preview.

Comparison and branch model

A human can use Compare to compare the selected revision with latest. Branch previews use URLs with ?branch=<name> and are read-only in AgentGrid.io. Branch commits appear in History; merging happens in the branch-producing workflow, after which the agent must verify the resulting main revision.

Never publish or restore from a branch preview. A branch URL tracks the named branch; a revision-pinned link remains fixed to one revision.

Operation semantics

Markdown autosaves. Save or ⌘S creates an explicit checkpoint rather than enabling persistence.

Agent procedure

Use exact artifact, revision, and branch identifiers supplied by the workflow. An artifact identifier, also called an artifact ID, selects one artifact. Inspect History before and after consequential operations. Duplication is non-idempotent: repeating it can create another artifact. If the response is lost, list recent artifacts before retrying.

A human must return to current state before editing or publishing. For recovery from an unwanted result, compare first and then ask the human to Restore if appropriate.

Related: Edit markdown · Canvas · Rename and duplicate

Questions and answers

Which identifiers must be exact? Use the supplied artifact, revision, and branch identifiers; never infer a branch name.

How is a branch merge verified? Return to the main artifact and confirm the resulting revision in History after the branch-producing workflow merges it.

What is the retry rule for Duplicate? If the response is lost, list recent artifacts before retrying because another request may create a second artifact.

Which recovery decision belongs to the human? After comparison, ask the human whether the historical revision should be restored into the original artifact.