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 and administrators can change store policy. Editors can create, update and delete memories. Readers can list and export records, and search semantically with credits. OAuth connections also need read/write consent in addition to membership roles. When service writes are disabled, write-capable roles still cannot create or update.

RolePermissions
ReaderBrowse and export; search with credits.
EditorRead, create, update and delete memories
AdministratorEdit memories, change policy and manage permitted memberships
OwnerEditor permissions and membership management.

Add a collaborator

As the owner, invite an email in the sharing panel and choose reader, editor or administrator access. The recipient signs up and verifies that same email to access the store. No separate invitation email is sent, so tell them you shared it. They connect to the same store with their own account. Do not share an 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

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.