Store and recall project context through MCP or CLI. Keep the core memory data on infrastructure you control, choose operating modes explicitly, and inspect provenance. The research pages describe versioned protocols and assumptions.
12 documented CLI workflows for storing context, recalling evidence, profiles, integrations and installation health. These are selected workflows rather than a claim of a complete command catalog.
Browse memory workflows →Carry project decisions and release requirements across agent sessions, then inspect the recalled evidence.
npm install -g superlocalmemory
slm setup
slm doctorOn 1 October 2026, an isolated mode A CLI run stored and recalled one synthetic release-checklist fact. Calibration was uncalibrated and answer confidence was null. This is not a retrieval accuracy benchmark.
Generation-fenced admission, policy registration, verifiable memory transactions, projection ownership, and hash-checkable completion manifests.
Dense, lexical, temporal, associative, and spreading-activation candidate producers fuse through one governed retrieval path.
Personal, named-profile, shared, and global scopes with role-aware access, provenance, export, and verified erasure.
Mode A local core, Mode B local model, and Mode C deliberate external provider usage with explicit network behavior.
Operate the same memory system from agent tools, terminal workflows, the dashboard, and framework adapters.
Feedback-driven learning, reusable retrieval paths, and context compression help agents retain useful context locally.
SuperLocalMemory 4.0: The Governed Memory Operating System for AI Agents
Varun Pratap Bhardwaj, 2026
Read on arXiv →