EtherPK has shipped version history for synced markdown notes, a critical safety layer for users letting AI agents roam their knowledge graphs. The feature, live in version 0.22.0, automatically snapshots pages and journal entries before destructive actions, ensuring that autonomous edits don’t permanently nuke your data.

Why Versioning Matters When Agents Have Write Access

While version control is standard for human collaboration, the calculus changes when AI agents can make broad changes at speed. EtherPK’s update addresses this asymmetry by creating versions automatically—either after editing pauses or immediately before deletes, renames, merges, and 'Replace all' operations. The system keeps deleted items recoverable, turning what was once a permanent data loss into a simple restore from the 'All Documents' sidebar.

The Mechanics of the Safety Net

The implementation is pragmatic: versions are created at most once every ten minutes per document per device, or instantly upon closing the tab. The UI provides a diff view with green additions and red removals, allowing users to inspect exactly what an agent changed before rolling back. Notably, restoring a version syncs across all devices and creates a new 'Before a restore' entry, making the undo chain transparent. However, Ctrl+Z won’t undo a restore; you have to explicitly restore the previous version.

Agent Permissions and Storage Tradeoffs

AI agents connected via EtherPK’s new MCP Server and Headless Client integrations can list and read versions using list_versions and read_version tools, but they cannot restore them. This human-in-the-loop constraint is a smart design choice—agents get context but not the power to rewrite history without permission. Storage costs are mitigated by aggressive thinning: edited versions are kept hourly for seven days, then daily, while action-triggered versions (deletes, renames) are never thinned. Local graphs are excluded entirely, as they rely on external version control.

Key Takeaways

  • Version history is exclusive to synced graphs in EtherPK 0.22.0+; local folders are unaffected.
  • AI agents have read-only access to version metadata and content via MCP tools, but restoration remains a human privilege.
  • Deleted documents and their versions are retained for a configurable period (30 days in examples) before permanent removal.
  • Encryption remains intact: versions are encrypted with the graph’s key before upload, preserving end-to-end privacy.

The Bottom Line

As agents become first-class citizens in note-taking workflows, versioning isn’t a luxury—it’s the rollback button that keeps autonomy from becoming chaos. EtherPK gets the threat model right by letting agents read history but forcing humans to approve restoration.