Where to use commands
After installing the OAK.memory plugin in Claude Code, use the full /oak-memory:memory-… command names below. Short forms such as /memory-config depend on the client and installed version. These are chat commands, not terminal commands.
In ChatGPT, Claude web or Codex with the cloud MCP connection, ask in natural language. Adding an MCP server does not install Claude Code slash commands. Verify the selected store before saving or changing anything.
Connect Claude CodeConnect, search and view
memory-connect guides cloud setup; memory-status verifies the profile, store, role and recording identity; memory-profile lists or switches configured profiles for this session.
memory-recall <query> explicitly searches for a topic. memory-graph [topic] shows memories and relationships. memory-graph-web opens the local plugin’s interactive graph; cloud users can view the graph in the memory dashboard. An empty search result is not proof that a fact never existed.
/oak-memory:memory-connect/oak-memory:memory-status/oak-memory:memory-profile/oak-memory:memory-recall PostgreSQL/oak-memory:memory-graph PostgreSQL/oak-memory:memory-graph-webCheck the connected store and my role, then recall our database architecture decisions.Save and organise
memory-save <fact> checks for a similar memory, then updates it or creates one. This is an explicit save request, including when local autosave is off. memory-organise [scope] reviews memories and links, adds or tunes relationships, and asks before lossy changes such as merging or deleting originals.
Saving and editing cloud memories require write permission, an eligible role, credits and enabled service writes. A command cannot bypass these requirements. Search also uses operation credits. Keep the subject and reason in each fact; check the returned result before assuming it was saved.
/oak-memory:memory-save The Atlas project uses PostgreSQL for transactional updates./oak-memory:memory-organise AtlasRemember that the Atlas project uses PostgreSQL because it needs transactional updates. Check for a similar fact before saving.Check and change memory policy
In the local Claude Code plugin, /oak-memory:memory-config shows the effective policy. Add a request to change scope (preferences, important, everything, custom), autosave or recall (minimal, balanced, aggressive). Local configuration changes apply after restarting Claude Code. Narrowing scope does not delete existing memories.
Cloud stores use getMemoryPolicy and updateMemoryPolicy, with written rules and recall values balanced, proactive or on_request. Ask to see the rules, or explicitly request a change. Policy edits require owner/admin permission and, with OAuth, write consent. A successful update in this conversation applies immediately; other conversations and dashboard edits apply at the next session. The local scope/autosave settings are not cloud policy fields.
/oak-memory:memory-config/oak-memory:memory-config preferences/oak-memory:memory-config autosave false/oak-memory:memory-config recall aggressiveShow the current memory policy.Change the policy so you only save facts when I explicitly ask, and recall context only on request. Preserve the other rules.