Sync
Sync keeps every connected client on the same page. Changes in one place propagate everywhere — automatically, over the same MCP connection.
Two-way sync
OmegaVault sync is bidirectional. When Claude reads your vault, any edits or new memories it creates flow back into OmegaVault. When you edit a memory in the OmegaVault app, every connected client sees the update on the next recall.
Conflict resolution
Memories are versioned, so conflicts are rare — but when they happen, OmegaVault keeps the most recent write and preserves the earlier version in history. You can always roll back.
What syncs
- The memory content and its tags.
- Collection assignments.
- Source attribution (the originating client is preserved across edits).
Knowledge-tool sync
Notion and Obsidian connectors push your structured memories out to those tools. This is one-way out of OmegaVault (with two-way editing where the tool supports it) — see Notion and Obsidian for the per-connector details.
Your memory is yours.
Capture once, carry everywhere.
Start Capturing