Repository navigation
OAK.memory v0.3.0 — atomic memory merges
OAK.memory's local stdio plugin now exposes atomic mergeMemories, matching the hosted cloud tool's input contract. This release includes synchronized, self-contained Claude Code and Codex bundles.
What's changed
- Merge 1–15 source memories into one retained target UUID using client-written text and exact original-content snapshots.
- Redirect directed, typed links and preserve the strongest colliding links. Preserve the target's creation and retrieval metadata, and archive all selected records and incident links in local
memory.merge_historybefore deleting absorbed sources. - Reject stale or foreign-store inputs and unconfigured policy scope. Roll back database failures without partial merging; check content and token limits before requesting an embedding.
- Include merges in cloud-profile write guards and update local curation instructions, tool descriptions and documentation.
- Upgrade MCP SDK to 1.32.1 and retain the separately prepared shared OAuth cloud package. This GitHub release publishes the local plugin; cloud directory submission and publication remain separate.
Validation
- Current-head Cursor review approved PR #6 with no Critical or High findings.
- PR and merged-master CI passed, including TypeScript/build checks, cloud bridge regressions, synchronized bundle checks and disposable PostgreSQL tests through actual stdio.
- PostgreSQL coverage includes typed link collisions, source history, stale/foreign inputs, provider and transaction rollback, replay, and concurrent content/link changes.
- The installed Claude Code plugin was updated to 0.3.0. A fresh session discovered
mergeMemoriesand successfully calledgetMemoryPolicy; no user memories were changed during installation verification.
PR #6 · Merged commit · CI
Update Claude Code
claude plugin marketplace update oak-memory
claude plugin update oak-memory@oak-memoryRestart Claude Code after updating. If the local plugin is disabled, enable it with claude plugin enable oak-memory@oak-memory.
Local PostgreSQL merges use the configured Ollama embedding provider. The client supplies the complete merged text; the server does not summarize it. The archive has no restore tool or automatic purge. Cloud-profile merges are forwarded to the selected hosted store and follow its authorization and credit policy.