v0.12.5

Full Changelog: v0.12.4...v0.12.5

v0.12.4

Full Changelog: v0.12.3...v0.12.4

v0.12.3

Full Changelog: v0.12.2...v0.12.3

v0.12.2

Full Changelog: v0.12.1...v0.12.2

v0.12.1

Full Changelog: v0.12.0...v0.12.1

v0.12.0 — Centroid-based auto-tagging

What's New

Automatic multi-facet tagging — Memories are now automatically tagged based on semantic similarity. When a memory is written, its embedding is compared against the centroid (average embedding) of each existing facet:value. Tags are applied when cosine similarity exceeds a configurable threshold.

For example, if you have 3+ memories tagged topics:cooking, writing a new memory about a recipe anywhere in the filesystem will auto-tag it with topics:cooking — no manual tagging needed.

Configuration

New optional fields in ~/.memfs/settings.json:

Setting	Default	Description
autotag_threshold	0.5	Cosine similarity threshold for auto-tagging
autotag_min_memories	3	Minimum tagged memories before a centroid is used

Details

• Centroids stored as unnormalized sums for exact incremental updates
• memfs reindex rebuilds all centroids from scratch
• Auto-tagging is non-fatal — errors are logged as warnings, never fail writes
• Works on both CLI writes and FUSE writes

Full Changelog: v0.11.0...v0.12.0

v0.11.0 — Merge-based cloud sync

Merge-based cloud sync with conflict detection

Multiple agents can now sync to the same Turso cloud database without overwriting each other's memories.

How it works

• Auto-merge: memories with unique filenames are merged automatically from both sides
• Conflict detection: same filename with different content → local version kept, remote version saved to ~/.memfs/conflicts/ for reconciliation
• No false conflicts: a last_push timestamp prevents your own pushes from echoing back as conflicts on subsequent syncs
• Deduplication: duplicate filenames (from repeated writes) are resolved by keeping the most recently updated version

Workflow

1. Agent A writes memories, runs memfs sync
2. Agent B writes memories (including one with the same filename), runs memfs sync
3. Agent B sees the conflict, reviews ~/.memfs/conflicts/, reconciles
4. Agent B runs memfs sync again — no conflict this time
5. Agent A runs memfs sync — gets Agent B's unique memories auto-merged, sees conflict on the shared file

Full Changelog: v0.10.8...v0.11.0

v0.10.8

Full Changelog: v0.10.7...v0.10.8

v0.10.7

Full Changelog: v0.10.6...v0.10.7

v0.10.6

Full Changelog: v0.10.5...v0.10.6