OAKOAK/memory
Dashboard
DocumentationReference
OAK.memory

Troubleshooting

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

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

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.