OAKOAK/memory
Dashboard
DocumentationGet started
OAK.memory

Using memory day to day

Once connected, talk naturally. Try remembering a preference, finding it in another conversation, and keeping it up to date.

Check your connection

Enable OAK memory in your AI app and send the request below. A store name, your role, and a successful memory listing establish that tools work. A completed login page or an Authenticate button alone does not prove this. A read-only connection cannot save or edit memories.

Example prompt
Check the current OAK memory store name and my permissions, then list saved memories. Do not save or edit anything yet.

Get started

Remember one preference

Use the example if it describes you, or change it first. A single fact with a clear subject is easier to find later. Ask the assistant to check for duplicates and show what was saved. “I will remember” is not a successful storage operation: check the tool result or the record in your dashboard.

Example prompt
I prefer concise answers in English. Check OAK memory for this preference, save it if needed, and show the actual storage result.

Find it in a new conversation

Open another conversation connected to the same store and ask the question below. Another supported AI can retrieve these memories when connected to that store with read access. Your entire chat history does not transfer automatically. If nothing is found, check the selected store, whether the fact was actually saved, and how specific your question is.

Example prompt
Find my preferred answer language and length in OAK memory. Do not guess if nothing is found.

Update a changed fact

When a preference or decision changes, ask to find and update the existing memory. State the old and new fact to avoid duplicates. If several records match, review the target first. The assistant uses identifiers from real search results; you do not need to invent or type an identifier.

Example prompt
Find my answer preference in OAK memory. Update the existing memory to say that I now prefer detailed explanations, then verify the result.

Connect related memories

Link facts about a shared topic such as travel, hobbies, or work to retrieve related context. Links do not justify inventing new facts. Open your store in the dashboard and select a memory node to inspect its details. Check who can read a shared store before adding personal information.

Example prompt
Find my travel planning memories in OAK memory and connect related ones. Use only facts actually stored.

Choose how automatic memory works

The default policy guides the AI to manage people, work, and projects mentioned in conversation automatically, while excluding general knowledge and AI answers themselves. Actual behavior depends on the AI loading that policy, using tools, and having permission. It does not guarantee every message is saved or every response searches memory. Your AI app’s own memory settings are separate from the OAK store policy.

A store owner or administrator can request the policy change below. It also affects other members of a shared store. A successful policy update in this conversation applies immediately; other conversations and web edits take effect at the next session. A read-only connection cannot change policy.

Example prompt
Change this store’s policy to save only information I explicitly ask you to remember. Show the updated rules.

Review and delete memories

Review the memory list and node details in the dashboard, or ask the AI to list records. The request below only lists deletion candidates: inspect them, then specify which memory to delete. Deletion is irreversible and removes associated links. Disconnecting does not delete stored memories. Copies already exported or shown in another app or conversation must be managed separately.

Example prompt
Find my answer preferences in OAK memory. Show deletion candidates first; do not delete anything yet.

Dashboard

Understand privacy and costs

Do not save passwords, API keys, or authentication codes as memories. Consider consent and the sharing scope when recording information about others. Separate personal and shared stores, and check the store and read/write permissions on the consent screen. Stored text may be sent to the embedding service for search, and retrieved results are processed by your chosen AI service.

Cloud use requires no terminal or database installation. Listing and deletion use no embedding operation credits, but request limits still apply. Semantic search, saving new memories, and changing content require credits and a working embedding service. AI subscription fees and OAK credits are separate; check your applicable balance and limits in account settings.

Documentation

Carry useful context into your next AI conversation. Create a private store, connect your assistant, and save important facts and decisions as memories.

Get started

Choose your service. Follow the steps for your environment, from setup to connecting your store.

Quickstart

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

Using memory day to day

Once connected, talk naturally. Try remembering a preference, finding it in another conversation, and keeping it up to date.

Connect OAK memory to ChatGPT

Connect ChatGPT to your OAK store so you can recall memories across conversations. Follow these steps to get started.

Connect Claude Desktop

Connect OAK memory in Claude Desktop or claude.ai through your Claude account’s connector settings.

Connect Codex

Follow the steps for your desktop app or CLI to connect OAK memory.

Core concepts

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

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.

Commands and conversation examples

Recall, save and manage memory from your conversation. Slash commands belong to the Claude Code plugin; connected web apps use natural-language requests.

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

Use memory for personal preferences, everyday plans, shared team context and development work.