Skip to content

docs: recommend nmem CLI for graph/relationship queries - #5

Merged
wey-gu merged 2 commits into
mainfrom
docs/nmem-graph-recommendation
Aug 24, 2026
Merged

docs: recommend nmem CLI for graph/relationship queries#5
wey-gu merged 2 commits into
mainfrom
docs/nmem-graph-recommendation

Conversation

@hawkingrei

Copy link
Copy Markdown
Contributor

Extends the existing "Direct nmem Use Is Always Allowed" section with an explicit recommendation to reach for nmem directly for graph/relationship queries (nmem graph expand, nmem graph evolves), which aren't in the default per-turn MCP tool set. Companion to the same note added across other plugins in nowledge-co/community.

The bundled commands cover the common per-turn loop; the nmem CLI can
do a lot more, including graph and relationship queries not exposed
in the default MCP tool set (see the community repo's
nowledge-mem-claude-code-plugin PR for the same note applied across
plugins).
hawkingrei added a commit to nowledge-co/community that referenced this pull request Aug 21, 2026
Same note as the earlier Claude Code plugin commit, applied to every
other plugin covering a client on the EXTERNAL_MCP_SURFACE.md
recognized-host list (Codex, Codex prompts, Kimi Code, Cursor,
CodeBuddy, Copilot CLI, OpenCode) -- they all share the same bounded
default MCP tool set, so the same "no graph queries in the default
set" gap and the same nmem CLI escape hatch applies to each.

Also reorders the recommendation: MCP tools first for the per-turn
loop, nmem CLI for anything beyond that -- not "prefer nmem over MCP"
in general, which the first wording could be misread as.

nowledge-mem-gemini-cli already had a "Direct nmem Use Is Always
Allowed" section; extended it in place (commits d2984d4, a838134 on
nowledge-co/nowledge-mem-gemini-cli#5) rather than adding a duplicate
section, and bumped this submodule's pointer to pick it up.
@wey-gu
wey-gu merged commit d2b8cc9 into main Aug 24, 2026
1 check passed
@wey-gu
wey-gu deleted the docs/nmem-graph-recommendation branch August 24, 2026 05:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants