Arkloop × Nowledge Mem
Select Nowledge as Arkloop's Memory provider for automatic Working Memory, recall, thread capture, and graph-aware distillation.
Native Arkloop Memory provider
Arkloop owns this integration. Select Nowledge in Arkloop's Memory settings; no separate community plugin or MCP prompt is required for its automatic lifecycle.
Arkloop can use Nowledge Mem instead of OpenViking as the backend for its Memory system. Once enabled, Arkloop reads context before a turn, persists the conversation to Mem, and can distill the saved thread after the turn.
Before You Start
- Nowledge Mem is running locally, or you have a reachable remote Mem server
- Arkloop is installed
- You can open Settings > Memory in Arkloop
For a local setup:
nmem statusConnect Arkloop
- Open Settings > Memory.
- Enable the Memory system.
- Select Nowledge as the provider.
- Choose Detect local instance, or enter the Base URL manually.
- Add the API key when the Mem server requires one.
- Set the request timeout if the default does not fit your network.
- Enable automatic organization if you want completed turns triaged and distilled.
The default local endpoint is:
http://127.0.0.1:14242What Happens Automatically
Before each relevant turn, Arkloop:
- reads Working Memory in parallel with recall
- builds a focused recall query from the recent conversation
- injects Working Memory into the stable system context
- adds relevant recalled knowledge to the current turn
After the turn, Arkloop:
- creates a
source=arkloopMem thread when needed - appends new messages with stable external links and idempotency keys
- can triage the saved conversation and distill durable knowledge when automatic organization is enabled
During compaction, Arkloop also asks the compactor to preserve still-active goals, decisions, and unfinished work from Working Memory.
Browse The Graph From Arkloop
Arkloop's provider also supports Mem connections and timeline queries. This lets Arkloop expose graph relationships and temporal context instead of treating Nowledge as a flat vector store.
Verify
Start a new Arkloop conversation and ask:
What does my Working Memory say I am focused on, and which related past decision is most relevant here?Then complete one short exchange and check Mem's Threads view. The saved thread should use Arkloop as its source and should grow as the conversation continues.
Troubleshooting
Detect local instance finds nothing
Run nmem status on the Arkloop machine. If Mem uses a custom port, enter its Base URL manually.
Arkloop recalls nothing
Confirm that Memory is enabled and Nowledge remains the selected provider. Empty Working Memory is valid; test memory search with a topic you know exists in Mem.
The thread exists but no durable memories appear
Thread capture and distillation are separate. Enable Arkloop's automatic organization setting, then confirm that Mem's background AI can run distillation for this server.
Remote requests fail
Check the Base URL, API key, request timeout, and whether the remote Mem endpoint is reachable from the Arkloop machine.