v1
Persist a user-edited document (non-AI autosave).
Persist a HUMAN-edited document — the editor’s debounced autosave + save-on-blur — WITHOUT an AI turn. Re-indexes the html into the target document (preserving its durable identity so it UPDATES the same Files entry), then saves it so pure typing is preserved AND other sessions with the same document open stay in sync. The AI-edit flow is unaffected (autosave saves first; a later AI result is merged with your saved edits). Non-billable, REST-only (a UI affordance, not an MCP tool).
POST
Persist a user-edited document (non-AI autosave).
Authorizations
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Headers
Body
application/json
Response
Successful Response
Previous
Restore a document another session archived, keeping your current edits (web app).Restore (un-archive) a document that was archived, re-linking it to this session and bringing
its content back. `document_id` is the session-local id (same as /save); the durable id is
recovered from the cached document. Idempotent: restoring an already-active (or never-archived)
document is a no-op. Non-billable.
Two shapes: WITHOUT a body (e.g. an AI agent restoring a document by id) the archived content is
restored as-is; WITH a body carrying the current editor HTML (the web app's "keep editing
(restores it)" choice after another session deleted the document) the document is restored AND the
supplied edits are saved on top, so it converges for everyone.
Next
Persist a user-edited document (non-AI autosave).

