OAK.memory Desktop Cloud 0.2.3

• Claude Desktop now reports the installed OAK.memory extension version consistently for single-store and multi-store installations.
• The hosted widget can link to a newer published bundle when the installed version is older.
• Existing store configuration and permissions carry over.

Download the .mcpb below and install it from Claude Desktop Settings → Extensions. Open a fresh chat after the extension reloads. Use the SHA-256 file to verify the download.

OAK.memory local 0.3.1 / Cloud sources 0.1.6

OAK.memory now recalls relevant context before answering and during work, and manages useful memories throughout the task according to each store's policy.

• Local stores default to automatic management. Cloud policies remain owned by their respective stores; local configuration never substitutes for them.
• Existing explicit restrictions remain. Invalid existing policy suspends all changes until repaired.
• listMemories uses bounded SQL pages. Refresh MCP tools after upgrading and follow nextCursor until hasMore=false for a complete audit.
• Upgrade: an absent local scope now enables automatic management. Set MEMORY_POLICY_AUTOSAVE=false before upgrading to retain manual saving. Local DB setup requires schema-owner permissions, including creation of tables, functions, indexes and triggers.
• Store identity, actual available tools and input schemas determine capabilities; uncertain writes are rechecked before retrying.

Validation: full tests and CI, current-head external review, isolated real PostgreSQL + Cloud HTTP/local stdio checks, and an actual Claude run that recalled and updated memory without an explicit memory request.

Cloud source packages 0.1.6 are attached. These files are not a marketplace resubmission; installed clients need a tool/package refresh.

Desktop Cloud 0.2.2: store-scoped proactive policies

Desktop Cloud 0.2.2 adds store-scoped proactive policy initialization while preserving 0.2.1 multi-store configuration and MCP Apps UI.

• Each configured cloud store supplies its own policy. Local policy settings never replace it.
• Existing Store ID/key and Stores JSON settings remain supported. Changes still require the existing extension write opt-in and server role; enabling writes follows that store's automatic-management policy.
• All mutations require an explicit store when multiple stores are configured. Listing cursors require their matching store ID.
• Failed or invalid policies suspend changes without falling back to another policy.

Validation: packaged single-store/four-store stdio and HTTP tests, source attribution, readonly and reader denial, revoked access, profile-switch races, UI resource forwarding and current-head CI/review.

Install the MCPB below and reconnect or start a fresh chat to refresh tools. This release does not resubmit a marketplace listing.

Desktop Cloud 0.2.1

Desktop Cloud 0.2.1 preserves multi-store configuration while adding OAK's interactive memory UI in compatible Claude Desktop hosts.

• Keeps existing Stores JSON and single-store credentials, write opt-in, source attribution and explicit mutation targets.
• Relays authenticated OAK UI resources, CSP and scoped result metadata without another-store fallback.
• All-store search retains grouped text results; choose one store in the UI to browse its cards and connections.
• Refreshes host tools and resources after profile changes; normalizes explicit store IDs.

Validation: full npm test, packaged single-store/four-store HTTP and stdio tests, final-head CI and code review. Existing connected-account permissions are not expanded by this update.

Download the MCPB below and keep your existing configured store IDs and personal keys. No local database, Docker or Ollama is required. This release does not change the separate OAuth cloud plugin package or its directory listing.

OAK.memory Desktop Cloud 0.1.1 — in-chat memory UI

OAK.memory Desktop Cloud now relays the hosted memory explorer into MCP Apps-compatible Claude Desktop versions.

• Memory cards, search, store selection and actual memory connections are provided by the OAK cloud server.
• Resource discovery, HTML/CSP and tool-result metadata pass through the authenticated cloud profile.
• Existing write opt-in, store roles and policy guards are preserved. Revoked connections fail explicitly; cached UI hints are hidden until recovery.
• No local database, Docker or Ollama is required.

Install the attached .mcpb through Claude Desktop Settings → Extensions. Existing 0.1.0 installations need this update to relay UI resources. The remote OAuth connection uses the hosted UI directly.

Validation: typecheck/build, cloud-profile isolation tests and real packaged stdio/HTTP roundtrips passed, including resource reads, CSP, file-URI rejection, revoked access, cached metadata recovery and legacy-server compatibility. Actual rendering also depends on the Claude Desktop version and refreshed connection metadata.

Desktop Cloud 0.1.0 — local MCP, cloud store

Install a local Claude Desktop extension and use your OAK cloud store. Download oak-desktop-cloud-0.1.0.mcpb, then open Settings → Extensions → Advanced settings → Install Extension. Configure the matching Store ID and named personal connection key in the extension settings. Never paste a key into chat.

Read-only by default. Enable Allow memory changes only when you want to permit saving, editing or deleting memories; store roles and server checks still apply. Autosave remains off. No Docker, Ollama, local database or separate Node installation is needed.

For company workspaces, local extension policy and allowlists still apply. Installing this package does not override organization restrictions. This package is for Claude Desktop on macOS and Windows, not Claude web/mobile or ChatGPT.

Instructions: https://github.com/fredriccliver/oak-memory-plugin/blob/master/docs/desktop-cloud.md

Validation: packaged stdio tests against an isolated HTTP server cover reads, explicit write opt-in, unknown mutation denial, reader denial, revoked keys, mismatched stores and no legacy local settings fallback. Actual installation and authenticated live calls in your Claude Desktop are separate from these tests. No production memory was written.

SHA-256: 72d526f9b0f89c9ef6a04bde455f8d948ce6c2442d18af899fb1bf1841e20a16

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_history before 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 mergeMemories and successfully called getMemoryPolicy; 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-memory

Restart 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.

oak-memory v0.2.0 — first public release

First public release of oak-memory — persistent vector+graph long-term memory for Claude Code, backed by Postgres + pgvector.

Install

/plugin marketplace add fredriccliver/oak-memory-plugin
/plugin install oak-memory

Then run the one-time setup (needs Docker + Ollama):

npm install
npm run setup

See the README for details, and the docs at https://openaikits.com.

Notes

• Licensed under the PolyForm Shield License 1.0.0 — free for any use except building a product that competes with OAK.memory / @openaikits/memory.
• Not zero-install: a marketplace install copies the plugin; you stand up the local Postgres + embedding model once via npm run setup.