Repository navigation
Getting Started
This page takes you from nothing to a working memory in about ten minutes: install, choose a mode, save one memory, find it again, connect your AI tool and open the dashboard. Each step says what you should see, so you can tell whether it worked. Everything here runs on your own computer. Detail behind any step is on the page it links to.
The easiest way is to let your AI agent do it: paste the install prompt from Installation into Claude Code, Codex, Cursor or any agent that can run commands. On macOS and Linux a one-line installer needs no Python or Node. If you prefer to type the commands, the routes below need Python 3.12 to 3.14 and, for npm, Node.js 18 or later. Apple Silicon Macs, 64-bit Windows and 64-bit Linux are supported.
npm install -g superlocalmemoryIf you prefer Python tools, pipx install superlocalmemory does the same job, or create a virtual environment and run python -m pip install superlocalmemory. Installing the package only puts the slm command on disk. It does not create your data folder, change any editor, start a background service or download a model. Platform notes, the other install routes and fixes for common errors are in Installation.
slm setupThe wizard asks first which mode to use. Mode A saves and recalls memories without a language model, and nothing leaves your device; it is the default and the right place to start. Mode B adds a model running on your own machine (Ollama, or any local server that speaks the OpenAI API). Mode C uses your own endpoint or a cloud provider and needs a key if it is a cloud service. You can change the mode later with slm mode a, slm mode b or slm mode c, followed by slm restart; Modes Explained says what each one changes. The wizard also lets you choose optional features and asks for consent before it connects any editor or installs a login service, and slm setup --auto takes every default without asking.
To download the embedding model ahead of time, run slm warmup. It is about 500 MB the first time, and it exits with an error if recall is not ready, so you know whether it worked.
slm remember "Our API uses JWT tokens with a 24-hour expiry. Refresh tokens last 30 days." --jsonThe reply is a receipt. It includes the id of the new memory, an operation_id, and a state of queryable, which means the memory can already be found by its wording while SLM finishes working out entities and meaning in the background. Add --sync if your next step needs that work to be finished first. Add --kind rule or --kind decision for something you want loaded at the start of later sessions (Memory Kinds). How a save works, including what happens if the computer stops halfway, is in How Remember Works.
slm recall "JWT token expiry"You should see the memory listed with a number in brackets. That number says how well the memory matches the question; it is not the chance that the memory is the right answer. slm trace "JWT token expiry" shows the same search with the score each retrieval channel gave. If you turn on the answer check, recall also tells you whether the top result actually answers the question. How recall works end to end is in How Recall Works.
slm status # mode, profile, data folder, database size
slm doctor # dependencies, the embedding worker and the background serviceslm health reports the state of the scoring and lifecycle layers. If something is wrong, Troubleshooting lists the symptoms and fixes.
slm connect --list # which editors were detected
slm connect cursor # write the connection for one named toolFor tools that read an MCP configuration, the entry is a command that runs slm mcp. Claude Code and Codex can also install a plugin with skills, agents and hooks that load context at the start of a session and capture decisions as you go. Each tool's steps are in IDE Setup, what the plugins contain is in Plugins, Skills and Hooks, and what automatic capture and recall do is in Auto-Memory.
slm dashboardThis opens the dashboard on your own computer, by default at http://localhost:8765. It shows what SLM knows, how it is health-checked, and the settings. Dashboard Tour walks through every screen.
| Command | What it does |
|---|---|
slm remember "..." |
Save a memory |
slm recall "..." |
Search your memories |
slm trace "..." |
Search and show the score from each channel |
slm list |
Show recent memories with the ids that update and delete take |
slm forget "..." |
Delete memories that match a query, after asking you |
slm delete <id> |
Delete one memory by its exact id |
slm status |
Mode, profile, data folder and database size |
slm mode a or b or c
|
Switch mode |
slm profile list, create NAME, switch NAME
|
Keep separate memory spaces (Profiles) |
slm connect |
Connect an AI tool |
slm dashboard |
Open the dashboard |
The full list, with every option, is in CLI Reference.
If you want to understand the design, start with Architecture. If you work in a team or need to show where an answer came from, read Governance and Privacy and Data Flow. If you have screenshots, PDFs or notes folders to search, read Pictures and Documents. If you want an AI app on the web to use your memory, read Web Access and Connected Apps.
Code: cli/setup_wizard.py, cli/main.py, cli/commands.py, core/config.py (daemon_port).
SuperLocalMemory: governed, local-first memory for AI agents. Home · Installation · Architecture · Privacy and Data Flow · CLI · MCP tools · FAQ
Part of Qualixar | Created by Varun Pratap Bhardwaj | GitHub · CHANGELOG
Platform boundary: Apple Silicon macOS, 64-bit Windows and 64-bit Linux. Linux covers x86_64 and ARM64. Intel Mac, 32-bit Windows and Windows on ARM are not supported.
SuperLocalMemory
Start here
How memory works
- Architecture
- How Remember Works
- How Recall Works
- Retrieval Score Contract
- Answer Check
- Memory Kinds
- Modes Explained
- Profiles
- Auto-Memory
- Active Memory
The living system
Governance and trust
- Governance
- Security, Company Mode and Teams
- Privacy and Data Flow
- GDPR
- Compliance
- Backup and Restore
- Cloud Backup
Beyond text
Connected systems
- Bots That Talk (SLM-Mesh)
- Connect Web Apps (steps)
- Web Access and Connected Apps
- Bounded Loops
- Framework Adapters
- Optimize
Operate and reference
- Dashboard Tour
- Configuration
- Embedding Models
- CLI Reference
- MCP Tools
- Capabilities and Operations
- Troubleshooting
- FAQ
Research
Archive