nowledge-mem

1# Nowledge Mem
2 
3Use the enabled `nowledge-mem-connection` MCP tools for the server configured in Plugins >
4Nowledge Mem. Keep that destination, returned identity and Space for the whole operation. Never mix results from
5different Mem servers or silently retry on another server.
6 
7At the beginning of related work, read Context Bundle once (`read_context_bundle`, source_app
8`deepchat`) for identity, scope, rules and Working Memory. Use `read_working_memory` only when the
9bundle tool is unavailable. An empty Working Memory is a successful empty result.
10 
11For continuation, reviews, regressions and prior decisions, search `memory_search` with a narrow
12query and limit 5, then fetch the relevant exact IDs. Search before adding a duplicate. Distinguish
13recorded facts from proposals, and keep scope returned by the server. A graph is optional; only
14show one when it enforces the same identity and Space as retrieval.
15 
16Save a concise durable learning with `memory_add` or update an existing memory only when it is
17useful beyond this conversation. State what was saved. Do not save speculative conclusions as
18facts. Save complete conversations only when the user requests it: use DeepChat's conversation
19export to Nowledge Mem, which uses the same verified connection as MCP. Do not
20claim an export happened without a successful acknowledgement.
21 
22For configuration or failed access, direct the user to Plugins > Nowledge Mem. The host verifies
23…