Opening a markdown artifact places the human directly in its rich editor. The underlying content remains markdown in a git repository, allowing people and agents to edit the same file.
What does the editor support?
The toolbar includes block styles, headings, font size, bold, italic, underline, strikethrough, inline code, text color, highlight, alignment, numbered lists, bullet lists, checklists, links, tables, emoji, and line spacing. Undo and redo are on the left; Save is on the right. Rich formatting is stored as markdown.
What is the required save procedure?
Auto-save is not live. The displayed “All changes saved” indicator is not reliable. A human must:
- Open the markdown artifact.
- Edit with the toolbar or markdown conventions such as headings, lists, quotes, code, and links.
- Select Save after every change.
- Verify that the change appears as the top History entry.
A save creates a Manual Edit history entry under the human's name and makes that saved version current for everyone. Unsaved screen content is invisible to agents and collaborators and is lost when navigating away or closing the tab.
A connected AI can be asked to update the same artifact, for example: Rewrite the intro of this artifact to be half as long, and keep everything else. or Add a risks section at the end of this doc.
What source structures are unsafe in editor sessions?
The rich editor rewrites the whole markdown file on save. Normal prose is unaffected, but machine-oriented structures may change:
- YAML frontmatter appears as document text and can be reformatted.
- Raw HTML and HTML comments can be rewritten or escaped.
When people and agents share a metadata-bearing artifact, keep load-bearing information in the visible body rather than frontmatter or comments.
How should concurrent editing work?
Teammates and agents edit the same artifact, and each saved change appears separately in History with its author. See Work on an artifact with your team.
If an agent changes an open artifact, the human should reload before continuing so the next human edit lands on the current version. If two people type concurrently, both changes enter History; reload to see the merged current version.
Constraints and recovery
- Formatting that markdown cannot express will not survive Save.
- App source is not editable in this editor. Use a connected AI or Edit with AI.
- To recover, select an earlier History entry and Restore it. See Version history.
- The only reliable proof of save is the new top History entry, not the save indicator.