AI makes mistakes! Undisk makes recovery instant: every write is versioned, every file is reversible.
See it heal →

​
How Versioning Works

Every file mutation (write, delete, move) creates an immutable version. Versions are content-addressed via SHA-256, so identical content deduplicates automatically.
  1. Agent calls write_file with new content
  2. Undisk MCP hashes the content (SHA-256), stores it, and creates a version entry
  3. Version entry records: timestamp, agent identity, content hash, file path, size
  4. Deletes create tombstone versions, so files disappear from listings without erasing their history
  5. Moves record both the old path and the new path, preserving rename history
  6. Previous versions are never modified. They are retained until your plan’s retention window expires (see Pricing and Limits).
  7. Call restore_version with any version ID to undo — creates a new head version with old content instead of rewinding history

​
Retention and purging behavior

  • Retention purges historical versions outside your plan window; it does not mutate surviving versions.
  • The latest live version remains readable unless the file itself is deleted.
  • When old versions expire, list_versions no longer returns them and restore_version on those IDs returns VERSION_EXPIRED.
  • File listings (list_files) reflect current live state, not expired historical snapshots.