OAKOAK/memory
Dashboard
DocumentationReference
OAK.memory

Troubleshooting

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

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.

If tools are missing, check that OAK memory is enabled in the AI app and try a new conversation. If web authentication finishes but the app still requests it, reconnect from the app with a fresh request. Do not reuse an old localhost callback link. If listing also fails, report the time, app name/version and error message, without passwords, keys or URLs containing authorization codes.

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

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.

If reading works but saving fails, check both your membership role and the connection’s write consent. Reconnect with the same account, choose the correct store and grant write access. Read-only members need the owner to change their role. Adding credits does not fix permissions.

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

Check identity and permissions

For an authentication failure, sign in again or check that the personal key belongs to the selected store. For a permission failure, ask the store owner to confirm your membership and role. Use currentMemoryStore to verify the connection. A reader cannot gain write access by receiving credits.

401 / 403Sign-in or access needs attention

Check request capacity and credits

A request limit and an empty credit balance need different actions. Wait and reduce call frequency for a rate limit. Check account settings and contact the operator for a credit shortage. If an upload pauses, preserve the same job and use its resume action rather than starting another import.

429Request rate or credits need attention

Check service availability

Search requires an embedding of the query, so it can fail even when saved memories are readable. An embedding configuration or provider failure is not fixed by changing store permissions. Try browsing saved records and contact the operator with the time, action and error message. Never include your API key in an issue report.

503Service or embedding configuration needs attention
Documentation

Install and use OAK Desk on your Mac, or connect OAK.memory to the AI tools you already use.

Get started

Install the published OAK.memory plugin in ChatGPT, use the Claude Code plugin or follow the connection guide for your app. Then sign in and verify 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.

Memory cards & explorer

See how OAK.memory appears inside ChatGPT and Claude Desktop, from a compact result card to the expanded memory explorer.

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

Add OAK.memory Cloud to Claude to connect your cloud stores. Choose the instructions for your personal or company account.

Connect Codex

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

Get started with Desk

Install the Mac app, connect one engine, and turn a first request into a result you can inspect.

Memory in Desk

Choose where memories live, see what reached a run, and control how Desk remembers decisions across conversations.

Run, review, and recover work

Work with files and ongoing tasks, inspect what changed, and choose when to apply or restore it.

Troubleshoot OAK Desk

Find the next step when an engine, memory store, attachment, or run needs attention.

Core concepts

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

Connect Claude Code

Connect your OAK cloud store to Claude Code with browser sign-in.

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.

Plugin updates

Check the published version and update steps for the OAK.memory installation you already use.

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.