Edit and revise
Artifacts are versioned documents, and there are two ways to move one forward: the browser for Markdown, the agent for everything.
Open the editor
Section titled “Open the editor”In the library, choose Open on a Markdown artifact, or go to
https://artifacts.example.com/edit/<artifactId>. HTML artifacts never open in the editor: their
Open action goes to the viewer, and the dashboard answers an editor URL for one with “HTML
artifacts use the viewer, not the markdown editor.”
Autosave
Section titled “Autosave”The editor keeps the document in a rich-text surface and saves as you type. The state next to the title tells you where you are:
| State | Meaning |
|---|---|
| Saved | The editor and the artifact are at the same revision |
| Saving | A save is in flight |
| Unsaved | Changes exist locally and have not been accepted yet |
| Conflict | The artifact moved on while you were editing; the editor turns read-only so nothing is lost |
A Conflict means a save arrived with a stale revision: another tab, another browser or the agent committed first. Reload the document to pick up the current revision and redo the edit against it. The server refuses the stale write rather than overwriting, which is why history stays linear.
Version history
Section titled “Version history”Open Version history in the editor’s top bar to list revisions newest first, with the current one marked. Restore on an older version asks first, then appends its content as a new revision. Earlier versions stay in the list, so a restore is itself reversible.
Comments
Section titled “Comments”Select text in the document and open Comments to start a thread anchored to that selection:
- The selection is quoted exactly as it appears in the stored source. When the text later changes, the thread is marked Outdated with “Text changed since this comment” instead of being re-anchored to different words.
- Replies attach to the thread root, one level deep.
- Threads can be resolved and unresolved.
- Comment bodies are capped at 4000 characters, quoted selections at 2000.
- Comments never change the document or create a revision.
Only Markdown artifacts accept comments.
Update through the agent
Section titled “Update through the agent”For HTML there is no dashboard editor, so the agent publishes the new revision. Two calls do the same for Markdown when the content lives in the conversation:
- Resend the document with
artifact_write, includingartifactIdandexpectedRevisionId. - Or patch lines with
artifact_edit_lines, which also requiresexpectedRevisionId.
Both refuse a stale revision and return the current revision id, so the agent can re-read and retry
instead of clobbering a browser edit. artifactId must be a canonical lowercase UUID; a readable slug
is refused before anything is written.
What is not editable
Section titled “What is not editable”- HTML artifact internals in the browser; use the agent.
- Titles, kinds and access settings in the editor; titles travel with a write, and access lives in Share and publish.