nowledge-co · wey-gu · Aug 24, 2026 · Aug 21, 2026 · Aug 21, 2026 · Aug 21, 2026
diff --git a/nowledge-mem-claude-code-plugin/README.md b/nowledge-mem-claude-code-plugin/README.md
@@ -193,6 +193,21 @@ Claude Code already has a clean override surface.
 
 Use `CLAUDE.local.md` for small personal memory-behavior changes such as "prefer saving Chinese notes" or "be more aggressive about searching prior release work" without forcing that rule on the whole team.
 
+## Beyond the default tools
+
+Use the MCP tools for the day-to-day per-turn loop. For anything beyond
+that -- including graph and relationship queries -- reach for the `nmem`
+CLI directly (already installed alongside this plugin). We recommend it
+whenever you hit a gap in the per-turn tool set:
+
+```bash
+nmem graph expand <memory-or-crystal-id> --depth 2
+nmem graph evolves <memory-id>
+```
+
+Run `nmem --help` (and `nmem graph --help`, `nmem <command> --help`, etc.)
+to see its full capabilities.
+
 ## Troubleshooting
 
 **nmem not found:** Install with `pip install nmem-cli` or `pipx install nmem-cli`. If you're in WSL, see the [WSL setup](#wsl-setup) above.

diff --git a/nowledge-mem-codebuddy-plugin/README.md b/nowledge-mem-codebuddy-plugin/README.md
@@ -57,6 +57,21 @@ Diagnostics are written to `~/.codebuddy/logs/nowledge-mem-hook.log` unless `COD
 
 Use `~/.codebuddy/CODEBUDDY.md`, project `CODEBUDDY.md`, or `.codebuddy/rules/*.md`. Do not edit installed marketplace files.
 
+## Beyond the default tools
+
+Use the MCP tools for the day-to-day per-turn loop. For anything beyond
+that -- including graph and relationship queries -- reach for the `nmem`
+CLI directly (already installed alongside this plugin). We recommend it
+whenever you hit a gap in the per-turn tool set:
+
+```bash
+nmem graph expand <memory-or-crystal-id> --depth 2
+nmem graph evolves <memory-id>
+```
+
+Run `nmem --help` (and `nmem graph --help`, `nmem <command> --help`, etc.)
+to see its full capabilities.
+
 ## Links
 
 - [CodeBuddy guide](https://mem.nowledge.co/docs/integrations/codebuddy)

diff --git a/nowledge-mem-codex-plugin/README.md b/nowledge-mem-codex-plugin/README.md
@@ -363,6 +363,21 @@ If you used `nowledge-mem-codex-prompts` before:
 | `distill` | `$nowledge-mem:distill-memory` |
 | *(none)* | `$nowledge-mem:status` |
 
+## Beyond the default tools
+
+Use the MCP tools for the day-to-day per-turn loop. For anything beyond
+that -- including graph and relationship queries -- reach for the `nmem`
+CLI directly (already installed alongside this plugin). We recommend it
+whenever you hit a gap in the per-turn tool set:
+
+```bash
+nmem graph expand <memory-or-crystal-id> --depth 2
+nmem graph evolves <memory-id>
+```
+
+Run `nmem --help` (and `nmem graph --help`, `nmem <command> --help`, etc.)
+to see its full capabilities.
+
 ## Troubleshooting
 
 - **"Command not found: nmem"**: update the plugin to `0.1.29` or newer. Its

diff --git a/nowledge-mem-codex-prompts/README.md b/nowledge-mem-codex-prompts/README.md
@@ -110,6 +110,21 @@ Then copy or merge the project guidance file:
 curl -O https://raw.githubusercontent.com/nowledge-co/community/main/nowledge-mem-codex-prompts/AGENTS.md
 ```
 
+## Beyond the default tools
+
+Use the MCP tools for the day-to-day per-turn loop. For anything beyond
+that -- including graph and relationship queries -- reach for the `nmem`
+CLI directly (already installed alongside this integration). We recommend
+it whenever you hit a gap in the per-turn tool set:
+
+```bash
+nmem graph expand <memory-or-crystal-id> --depth 2
+nmem graph evolves <memory-id>
+```
+
+Run `nmem --help` (and `nmem graph --help`, `nmem <command> --help`, etc.)
+to see its full capabilities.
+
 ## Troubleshooting
 
 - **"Command not found: uvx"** → Install uv with `curl -LsSf https://astral.sh/uv/install.sh | sh`

diff --git a/nowledge-mem-copilot-cli-plugin/README.md b/nowledge-mem-copilot-cli-plugin/README.md
@@ -133,6 +133,21 @@ Copilot CLI already has a native instruction layer. Use that as your override pa
 
 Keep the plugin for lifecycle hooks and capture. Put your custom memory behavior in Copilot instruction files so updates do not wipe it out.
 
+## Beyond the default tools
+
+Use the MCP tools for the day-to-day per-turn loop. For anything beyond
+that -- including graph and relationship queries -- reach for the `nmem`
+CLI directly (already installed alongside this plugin). We recommend it
+whenever you hit a gap in the per-turn tool set:
+
+```bash
+nmem graph expand <memory-or-crystal-id> --depth 2
+nmem graph evolves <memory-id>
+```
+
+Run `nmem --help` (and `nmem graph --help`, `nmem <command> --help`, etc.)
+to see its full capabilities.
+
 ## Troubleshooting
 
 **nmem not found:** Install with `pip install nmem-cli` or `pipx install nmem-cli`. If you're in WSL, see the [WSL setup](#wsl-setup) above.

diff --git a/nowledge-mem-cursor-plugin/README.md b/nowledge-mem-cursor-plugin/README.md
@@ -108,6 +108,21 @@ Verify capture with a distinctive phrase from the session:
 nmem t search "distinctive phrase"
 ```
 
+## Beyond The Default Tools
+
+Use the MCP tools for the day-to-day per-turn loop. For anything beyond
+that -- including graph and relationship queries -- reach for the `nmem`
+CLI directly. We recommend it whenever you hit a gap in the per-turn
+tool set:
+
+```bash
+nmem graph expand <memory-or-crystal-id> --depth 2
+nmem graph evolves <memory-id>
+```
+
+Run `nmem --help` (and `nmem graph --help`, `nmem <command> --help`, etc.)
+to see its full capabilities.
+
 ## Spaces And Identity
 
 Spaces are optional. The startup and capture hooks honor `NMEM_SPACE` (or legacy `NMEM_SPACE_ID`), `NMEM_AGENT_ID`, and `NMEM_HOST_AGENT_ID` when Cursor is launched in a stable lane.

diff --git a/nowledge-mem-gemini-cli b/nowledge-mem-gemini-cli
diff --git a/nowledge-mem-kimi-code-plugin/README.md b/nowledge-mem-kimi-code-plugin/README.md
@@ -189,6 +189,21 @@ Use Kimi Code's own instruction surfaces for personal behavior:
 
 Do not edit files under `$KIMI_CODE_HOME/plugins/managed/`; those are managed copies and can be replaced by Kimi Code updates.
 
+## Beyond the default tools
+
+Use the MCP tools for the day-to-day per-turn loop. For anything beyond
+that -- including graph and relationship queries -- reach for the `nmem`
+CLI directly (already installed alongside this plugin). We recommend it
+whenever you hit a gap in the per-turn tool set:
+
+```bash
+nmem graph expand <memory-or-crystal-id> --depth 2
+nmem graph evolves <memory-id>
+```
+
+Run `nmem --help` (and `nmem graph --help`, `nmem <command> --help`, etc.)
+to see its full capabilities.
+
 ## Links
 
 - [Kimi Code guide](https://mem.nowledge.co/docs/integrations/kimi-code)

diff --git a/nowledge-mem-opencode-plugin/README.md b/nowledge-mem-opencode-plugin/README.md
@@ -177,6 +177,21 @@ For multi-agent orchestrators, set `NMEM_AGENT_ID=<agent-slug>` per spawned Open
 
 Shared spaces, default retrieval, and agent guidance still come from Mem's own space profile. OpenCode should pick the lane once, not invent a second plugin-local memory partition.
 
+## Beyond the default tools
+
+Use the MCP tools for the day-to-day per-turn loop. For anything beyond
+that -- including graph and relationship queries -- reach for the `nmem`
+CLI directly (already installed alongside this plugin). We recommend it
+whenever you hit a gap in the per-turn tool set:
+
+```bash
+nmem graph expand <memory-or-crystal-id> --depth 2
+nmem graph evolves <memory-id>
+```
+
+Run `nmem --help` (and `nmem graph --help`, `nmem <command> --help`, etc.)
+to see its full capabilities.
+
 ## Troubleshooting
 
 - **nmem not found.** Install with `pip install nmem-cli`, or on Arch Linux `yay -S nmem-cli` / `paru -S nmem-cli`, then run `nmem status` to verify.