OAKOAK/memory
Dashboard
DocumentationCore concepts
OAK.memory

Core concepts

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

Memories and relationships

A memory is a piece of natural-language context with a stable UUID. Relationships connect memories that refer to each other. Record a specific fact or decision rather than an entire conversation. A recording author identifies who saved a memory, not necessarily the person described in its content.

Stores and access

A store is the boundary for a private or shared collection of memories. Each store has members and roles. The selected API key is bound to one account and one store. Seeing a store in a list does not grant access, and selecting a different store does not merge their contents.

How retrieval works

Semantic search finds memories related to a question; graph relationships add connected context. The assistant follows the selected store’s policy to decide how to use that context. Returned UUIDs identify the memories to update or link. Use those UUIDs directly instead of inventing an ID or using a display position.

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.