Nlm Memory

Memory for agents that work across tools and projects

NLM indexes AI sessions into a local searchable store. Recover an earlier decision, inspect the source conversation, and mark outdated reasoning as superseded. An agent using one runtime can retrieve work captured from another.

Local-first. Source-backed. Correctable. SQLite is the default; PostgreSQL with pgvector is also supported. No NLM account is required for local use. Classification and embedding providers are configurable: choosing a remote provider sends relevant content to it. See data flow and security.

Install · Demo · Runtimes · API · Evidence · Roadmap

Release status

Full status and upgrade notes. Source availability is not a promise that an experimental feature has passed its evaluation gate.

Install

Node.js 22 or newer and an embedding/classification provider are required. The setup wizard helps configure providers and the runtimes you use.

npm install -g nlm-memory
nlm setup
nlm recall "why did we change the database?"

Open http://localhost:3940/ui to browse the timeline and search. macOS and Linux support managed daemon setup; Windows currently uses manual nlm start.

If you use local Ollama, make the configured classifier and embedding models available before indexing. A cloud classifier is optional, and receives session content. Configuration · Security.

What an agent can do

MCP over the local daemon's /mcp endpoint is the default connection. Automatic hooks depend on the runtime; capture support does not imply hook support. Per-prompt ambient recall is off by default on fresh installs. Runtime matrix and hooks · MCP/HTTP reference.

Try a safe demo

The project-memory demo runs on a disposable SQLite database using fictional Atlas and Beacon sessions. It demonstrates cross-runtime evidence, a superseded decision, a property filter, and an explicit ownership correction.

git clone https://github.com/pbmagnet4/nlm-memory.git
cd nlm-memory
npm ci
npm run demo:memory

No classifier, embedding provider, daemon or real transcript is used. The demo calls the storage APIs directly; it is a behavior walkthrough, not an end-to-end capture or answer-quality benchmark.

What has been measured?

Methods, dates, configuration and limitations: evaluation guide. Older measurements describe their recorded versions, not an assumed score for current main.

Documentation

• Runtime integrations and hooks
• MCP tools and HTTP API
• Context retrieval and response budgets
• Editable timeline
• Canonical memory properties — prerelease
• Configuration
• Signals and optional code exemplars
• Digest and UI
• Security and vulnerability reporting
• Roadmap and contribution priorities

Development

npm ci
npm run typecheck
npm test
npm run build
npm run verify:codex-release -- --check-packed

dist/ is generated and not tracked. The packed package contains the distributable and plugin assets. PostgreSQL contracts are opt-in locally through NLM_PG_TEST_URL; GitHub CI provides pgvector and runs that suite.

Keep examples synthetic and never include a real memory database, provider credentials or private transcripts in an issue or pull request. Contribution guide.

Apache 2.0 — LICENSE.