A Native Memory Provider
Arkloop owns this integration. In Settings > Memory, enable Memory and choose Nowledge instead of OpenViking. Use Detect local instance for a local Mem server, or enter the Base URL, API key, and timeout for a protected or remote server.
What Happens Automatically
- Working Memory is loaded into the stable session context
- Relevant memories are searched before a turn and added only when they pass Arkloop's recall policy
- Arkloop conversations are created and incrementally appended as
source=arkloopthreads - Stable external thread links and idempotency keys prevent duplicate appends
- When automatic organization is enabled, Arkloop can triage and distill the saved conversation after a turn
- Connections and Timeline remain available through Arkloop's graph-aware Memory views
This is not a generic MCP fallback. Arkloop implements Mem as a first-class Memory provider and owns the lifecycle that makes recall and capture automatic.
