OAKOAK/memory
Dashboard
DocumentationCore concepts
OAK.memory

Share a memory store

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

Choose the right role

Owners manage membership. Editors can create and change memories. Readers can view and export saved memories and search when they have credits. Service write availability can still prevent an editor or owner from creating or updating a memory.

RolePermissions
ReaderBrowse and export; search with credits.
EditorRead, create and update memories.
OwnerEditor permissions and membership management.

Add a collaborator

As the owner, open the store’s sharing panel and enter an existing, email-confirmed account. Choose reader or editor access. No invitation email is sent by this action. The collaborator selects the shared store in their own dashboard and connects with their own key; do not share your personal API key.

Shared context, individual usage

Search and embedding operations use the requesting account’s credits and limits, including in a shared store. Sharing a store does not transfer credits or raise a collaborator’s usage tier. If a collaborator can browse but cannot search, check their available credits and effective limits.

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.