OAKOAK/memory
Dashboard
DocumentationReference
OAK.memory

Usage tiers and limits

Understand which limits your account shares, how operation credits work and what to do when a request is refused.

What counts toward a limit

All cloud MCP tool calls and protected memory data routes share your account’s rolling 60-second request budget. Calls made with different keys, stores or agents still belong to the same account. Embedding operations have an additional per-minute budget; both checks can apply to a search or write.

LimitShared byWhere to check
Total requests / minuteAll stores, keys and agents on one accountAccount settings
Embedding operations / minuteThe requesting accountAccount settings
Operation creditsThe requesting account, including shared storesAvailable credit balance

Find your effective usage tier

Open account settings in the dashboard to see your effective tier and its total-request and embedding-operation limits. An active account assignment determines the tier. When an assignment expires, the default tier applies. Buying or receiving operation credits does not change your tier. Subscription purchases are not currently available.

Request limits and credits are different

A request limit controls how quickly you can use the service. An operation credit allows a cost-bearing embedding operation, such as search, creation or update. You may have credits left and still hit a rate limit, or have request capacity but no credits for search. Failed operations follow the credit refund rules; a request reservation still remains in the rolling time window.

Signup includes 1,000 credits valid for 30 days. 50 daily free credits do not roll over. Storage limits depend on your plan; request rates depend on your account usage tier. Free listing, graphs and exports also count toward the request rate limit.

Create, update and semantic recall cost 1 credit each. Failed operations are refunded. Listing, export, deletion and link management are free.

Resume after a limit

When a request is rejected for a confirmed rate limit, stop repeated retries and wait for earlier requests to leave the 60-second window. Reduce concurrent agents or pace a large import. For example, if your account limit is 100 requests per minute, two agents making 60 calls each would exceed that shared budget. This is an example, not a promise of your account’s current limit.

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.