OAKOAK/memory
Dashboard
DocumentationResources
OAK.memory

Local plugin setup

Run memory on your own machine instead of using a hosted cloud store. This has a separate database and setup process.

Before you start

The local plugin requires Node.js 22+, Docker for PostgreSQL with pgvector, and Ollama for local embeddings. These are local-mode requirements; hosted cloud users do not need a local database or Ollama. Keep local and hosted databases separate because their embedding configurations may differ.

Install OAK.memory

Install the plugin in Claude Code using the commands below. Follow the installed plugin’s setup guide for its current dependency and database configuration. The cloud store profile workflow is separate from configuring a local database.

Claude Code
/plugin marketplace add fredriccliver/oak-memory-plugin
/plugin install oak-memory@oak-memory

Configure and verify

In the installed plugin directory, follow its documented npm install and npm run setup steps. Review the generated local settings, restart Claude Code and test retrieval before relying on persistent memory. The /memory-config command opens the plugin configuration workflow. Consult the plugin’s GitHub documentation for the current local setup details.

Terminal
git clone https://github.com/fredriccliver/oak-memory-plugin.git
cd oak-memory-plugin
npm install
npm run setup
GitHub
Continue reading
TroubleshootingGuides
Documentation

Persistent memory for your AI workflow. Start with a private store, connect Claude Code, and carry useful context from one session to the next.

Quickstart

Create a store, connect your assistant and save your first memory. The cloud service runs the database for you.

Core concepts

Understand memories, stores and retrieval before connecting them to a longer workflow.

Connect ChatGPT or Claude

In your app’s custom MCP or connector settings, add https://www.openaikits.com/api/mcp and choose OAuth. Sign in to OAK, choose a store and approve access. You return to your app automatically. Automatic registration needs no API key, client ID or secret.

Connect Claude Code

Use a personal key and store profile to connect the OAK.memory plugin to hosted memory.

Share a memory store

Give collaborators access to a shared context while keeping each account’s identity and usage separate.

MCP tool reference

The cloud MCP endpoint exposes tools for store discovery, retrieval and memory changes. Your connection supplies the account and store context.

Usage tiers and limits

Understand which limits your account shares, how operation credits work and what to do when a request is refused.

Troubleshooting

Identify whether an issue comes from your connection, permissions, usage or the embedding service.

Local plugin setup

Run memory on your own machine instead of using a hosted cloud store. This has a separate database and setup process.

Guides

Practical paths for using memory in a personal project, a shared team store or a workflow with several agents.