NLM
Local searchable store for AI sessions with recall, source inspection and correction.
Tested on macOS, Linux and WindowsKnown vulnerabilities
Use it
Before you install: known vulnerabilities
pickfit found 8 known high or critical vulnerabilities in the packages a fresh install brings (OSV.dev, 3 Nov 2026). Weigh this before you install it.
npm:adm-zip 0.5.18adm-zip: Uncontrolled memory allocation via the declared uncompressed size (DoS) (GHSA-7q85-xj36-vmfc, high, fixed in 0.6.1)npm:sharp 0.34.5sharp inherited vulnerabilities in libvips: CVE-2026-33327, CVE-2026-33328, CVE-2026-35590, CVE-2026-35591 (GHSA-f88m-g3jw-g9cj, high, fixed in 0.35.0)
See 6 more
npm:adm-zip 0.5.18— GHSA-8238-w5pm-2374 (high), fixed in 0.6.1npm:adm-zip 0.5.18— GHSA-j5f4-cc29-5x44 (high), fixed in 0.6.1npm:adm-zip 0.5.18— GHSA-rcw4-f5rp-g42v (high), fixed in 0.6.1npm:adm-zip 0.5.18— GHSA-xcpc-8h2w-3j85 (high), fixed in 0.6.0npm:sharp 0.34.5— GHSA-rgj7-g3m4-5g8c (high), fixed in 0.35.4npm:sharp 0.34.5— GHSA-wq5f-xc86-pv6w (high), fixed in 0.35.5
macOS arm64
You need first
- Runtimes:
Node.js 22 or newer
install nlm-memory via npm global
npm install -g nlm-memory
Check that it works
nlm --versionThe output should contain “0.21.20”.
First thing to try
git clone https://github.com/pbmagnet4/nlm-memory.git /tmp/nlm-memory 2>&1 | tail -n 20cd /tmp/nlm-memory && npm ci 2>&1 | tail -n 20cd /tmp/nlm-memory && npm run demo:memory 2>&1Clone the project repository, run npm ci inside it, then run npm run demo:memory to see a walkthrough of recall, source inspection and correction.
Linux x86_64
You need first
- Runtimes:
Node.js 22 or newer
Install nlm-memory via npm
npm install -g nlm-memory
Check that it works
nlm --version 2>&1The output should contain “0.21.20”.
First thing to try
nlm recall "why did we change the database?" 2>&1Clone the project repository, run npm ci inside it, then run npm run demo:memory to see a walkthrough of recall, source inspection and correction.
Windows x86_64
You need first
- Runtimes:
Node.js 22 or newer
Install nlm-memory globally via npm
npm install -g nlm-memory
Check that it works
nlm --versionThe output should contain “0.21.20”.
First thing to try
nlm recall "why did we change the database?"Clone the project repository, run npm ci inside it, then run npm run demo:memory to see a walkthrough of recall, source inspection and correction.
What it does
- Recover earlier decisions across sessionsTested
How to use it
- Clone the repository and run
npm ciin its folder. - Run
npm run demo:memoryto see earlier decisions recalled across sessions.
- Clone the repository and run
- Inspect the source conversation behind a memoryTested
How to use it
- Clone the repository and run
npm ciin its folder. - Run
npm run demo:memoryand read the source evidence shown for each recalled item.
- Clone the repository and run
- Mark outdated reasoning as supersededTested
How to use it
- Clone the repository and run
npm ciin its folder. - Run
npm run demo:memoryto see an outdated entry corrected and marked as superseded.
- Clone the repository and run
- Recall structured facts with where they came fromTested
How to use it
- Clone the repository and run
npm ciin its folder. - Run
npm run demo:memoryto see facts recalled with their source, such as who set them.
- Clone the repository and run
How far pickfit got
macOS arm64
- Installs
- Starts
- 4 of 4 features work
- Works offline
Linux x86_64
- Installs
- Starts
- 0 of 4 features work
- Works offline
Windows x86_64
- Installs
- Starts
- Main function works
- Works offline
Other systems
Good for
- Recover an earlier decision
- inspect source conversation
- correct outdated memory
How pickfit tested it
Each run starts from a clean machine and follows the steps above. How pickfit verifies
macOS arm64
Its main function works
- Replayed from scratch
- Works offline
- Checked on 1 Nov 2026
- Version 0.21.20
Differences the test machine hit
- README: npm install -g nlm-memory
In the test: npm install emits warnings about deprecated boolean@3.2.0 and install-scripts needing allowScripts for onnxruntime-node, sharp, protobufjs, but install still succeeds
Linux x86_64
Its main function works
- Replayed from scratch
- Works offline
- Checked on 30 Oct 2026
- Version 0.21.20
Differences the test machine hit
- README: npm ci then npm run demo:memory
In the test: source-checkout demo (npm ci) fails building better-sqlite3 (node-gyp rebuild) — box lacks C toolchain; used installed package dist + migrations directly instead - README: demo shows property filter and ownership correction
In the test: stable npm 0.21.20 has sessions/facts/supersedence but no property catalog APIs; property filter and ownership correction need prerelease next channel
Windows x86_64
Its main function works
- Replayed from scratch
- Works offline
- Checked on 31 Oct 2026
- Version 0.21.20
Differences the test machine hit
- README: (Windows steps)
In the test: pickfit ran these steps in PowerShell 7 (pwsh 7.6.9) as a standard user; the built-in Windows PowerShell 5.1 is not verified and does not run `&&`.