| name | nowledge-mem |
| description | Use Nowledge Mem from Kimi Work for startup context, memory search, durable saves, thread search, and Kimi Work transcript import. |
Nowledge Mem is the user's cross-tool memory. Use it to start with the right context, recall prior work, save durable decisions, and make Kimi Work sessions searchable from other AI tools.
Startup Context
At the beginning of a meaningful session, or when resuming work, read Context Bundle if the Nowledge Mem MCP server is connected. It includes owner context, AI Identity, active rules, active space, and Working Memory.
If MCP is not connected, use the CLI fallback:
nmem --json context --source-app kimi-work
If that fails on an older nmem, use:
nmem --json wm read
Do not read both Context Bundle and Working Memory unless the user asks. Summarize only the parts relevant to the current task.
Recall
Search memory when the user references prior work, asks for rationale, resumes a named project, investigates a regression, or asks about something that may already have been decided.
Prefer MCP when available:
memory_search for durable decisions, preferences, procedures, and learnings.thread_search when the user asks about prior conversations.thread_fetch_messages only after a thread result is relevant.
CLI fallback:
nmem --json m search "what to look up"
nmem --json t search "conversation to find" --source kimi-work -n 5
For broad browsing across memories, threads, wiki pages, and artifacts, use the Knowledge Filesystem through MCP mem_fs when available, or:
nmem fs recall "topic" --in /memories -k 5
nmem fs grep "exact phrase" /threads
Save Durable Knowledge
When a meaningful decision, reusable procedure, user preference, correction, or non-obvious lesson appears, save it. Search first to avoid duplicates.
Prefer MCP:
memory_search for an existing memory.memory_update if the existing memory should evolve.memory_add for a new durable memory.
CLI fallback:
nmem --json m search "existing concept"
nmem --json m add "content" -t "Title" --unit-type decision -l "label" -s kimi-work -i 0.8
Use one strong memory instead of several weak notes.
Import Kimi Work Threads
Real thread sync is local to the machine where Kimi Work stores its session files. MCP is not the transcript-import layer.
Kimi Work does not expose lifecycle hooks today. If the user asks to import Kimi Work conversations, preview first:
nmem t sync --from kimi-work --limit 20
Then import:
nmem t sync --from kimi-work --apply
If Kimi Work stores sessions somewhere else, pass the embedded runtime folder:
nmem t sync --from kimi-work --session-dir "/path/to/kimi-work/home/sessions" --apply
This works for local and remote Nowledge Mem because nmem reads local Kimi Work files and uploads normalized threads to the configured Mem server.
Status
When setup seems broken or the user asks whether Mem is connected:
nmem --json status
If the desktop app is on the same machine, nmem usually comes from the app. If Kimi Work runs on another machine, install the standalone CLI:
python3 -m pip install --user nmem-cli
Space And Identity
If the host process has NMEM_AGENT_ID, NMEM_HOST_AGENT_ID, or NMEM_SPACE, let nmem use those environment variables. Do not treat source_app=kimi-work as an AI Identity; it is only provenance.
User Overrides
For personal Kimi Work behavior, use Kimi Work's own instruction surfaces if they are available. Do not edit installed connector files under the embedded runtime's plugins/managed/ directory; this installer replaces that managed copy on update.
