Markdown artifacts open in a rich editor and save continuously. The save indicator reports whether your current edits have reached AgentGrid.io; an explicit Save or ⌘S creates a named point in History rather than being required for ordinary persistence.
Edit and autosave
Use the toolbar for headings, emphasis, lists, checklists, links, tables, code, colors, alignment, and other supported markdown formatting. While you type, autosave sends changes continuously. Wait for the indicator to show the saved state before closing the tab.
If saving is interrupted, keep the page open while the editor retries. Offline edits remain local until reconnection; after reconnecting, wait for the saved indicator and review the current document. If the editor reports a conflict or the result is not what you intended, use Version history to compare and recover.
Checkpoints and live collaboration
Use Save or ⌘S when you want an explicit History checkpoint. Teammates can edit simultaneously; presence and remote selections appear where supported. Their work updates live rather than requiring routine reloads. Human and agent changes remain attributed in History.
If collaborators produce an unwanted saved result, do not create competing copies. Open History, compare the relevant revision with latest, and restore the version you need.
Source boundaries
The editor stores markdown and may normalize the whole file. Formatting that markdown cannot express may not survive. YAML frontmatter, raw HTML, and HTML comments can be reformatted or escaped, so keep important shared instructions in visible document content.
Mermaid diagrams
Use a fenced mermaid block:
```mermaid
flowchart LR
A[Draft] --> B[Review]
B --> C[Publish]
The editor provides **Source**, **Split**, and **Diagram** modes. Mermaid renders in the editor, History, and published pages. A parse error falls back to source without deleting it. Include accessible metadata such as `accTitle` and `accDescr` in diagrams.
## Agent route and recovery
A connected agent with write capability and workspace access can update the same saved artifact. Ask for a specific change and verify it in History. For persistent save, reconnect, or conflict failures, see [Troubleshooting](/docs/help/troubleshooting).
Related: [Work with your team](#share-with-your-team) · [Review and comments](#review-comments)
## Questions and answers
**Do I need to select Save after every edit?**
No. Markdown autosaves continuously. **Save** or `⌘S` creates a named History checkpoint.
**When is it safe to close the page?**
Wait until the save indicator shows that current edits reached AgentGrid.io.
**What happens to offline edits?**
They remain local until reconnection. Keep the page open, reconnect, wait for saved state, and review the document.
**What happens when Mermaid source has an error?**
The editor falls back to showing the source without deleting it.