Autosave writes every change inside 📝Version History automatically, about a second after you stop typing — no save button, nothing to remember. It exists so writing never competes with the mechanics of saving; the memo is always current on the server, not just on screen. It's for every write in MythOS, on every editable surface.
Key Capabilities
- Debounced save — changes save roughly 800ms after you stop typing
- Save status indicator — a small "Saving…" / "Saved" label shows the current state
- Optimistic locking — each save carries a content version, so a stale save can't silently overwrite newer content
- Failure toast — a save error surfaces as a top-right notification, not a silent failure
Getting Started
Nothing to set up — just write. The save indicator near the memo title shows the current status.
FAQ
- Do I need to save manually? No — autosave handles every change automatically.
- What happens if a save fails? A toast notification appears in the top right, and the error is logged so it can be investigated.
- What if I have the same memo open in two places? Optimistic locking (a content version on every save) prevents a stale save from silently overwriting newer content — a conflicting save is rejected rather than applied blind.
- Does autosave create a new version every time? No — edits within a short window coalesce into one version log entry rather than one per keystroke; see 📝Version Control for the full history system.
Related
- 📝Version Control — the retained history autosave feeds