pickfit

BrowseDeveloper CLIs

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.18 adm-zip: Uncontrolled memory allocation via the declared uncompressed size (DoS) (GHSA-7q85-xj36-vmfc, high, fixed in 0.6.1)
  • npm:sharp 0.34.5 sharp 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

macOS arm64

You need first

  • Runtimes: Node.js 22 or newer
  1. install nlm-memory via npm global

    npm install -g nlm-memory

Check that it works

nlm --version

The 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 20
cd /tmp/nlm-memory && npm ci 2>&1 | tail -n 20
cd /tmp/nlm-memory && npm run demo:memory 2>&1

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.

Linux x86_64

You need first

  • Runtimes: Node.js 22 or newer
  1. Install nlm-memory via npm

    npm install -g nlm-memory

Check that it works

nlm --version 2>&1

The output should contain “0.21.20”.

First thing to try

nlm recall "why did we change the database?" 2>&1

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.

Windows x86_64

You need first

  • Runtimes: Node.js 22 or newer
  1. Install nlm-memory globally via npm

    npm install -g nlm-memory

Check that it works

nlm --version

The 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 sessions
    How to use it
    1. Clone the repository and run npm ci in its folder.
    2. Run npm run demo:memory to see earlier decisions recalled across sessions.
    Tested
  • Inspect the source conversation behind a memory
    How to use it
    1. Clone the repository and run npm ci in its folder.
    2. Run npm run demo:memory and read the source evidence shown for each recalled item.
    Tested
  • Mark outdated reasoning as superseded
    How to use it
    1. Clone the repository and run npm ci in its folder.
    2. Run npm run demo:memory to see an outdated entry corrected and marked as superseded.
    Tested
  • Recall structured facts with where they came from
    How to use it
    1. Clone the repository and run npm ci in its folder.
    2. Run npm run demo:memory to see facts recalled with their source, such as who set them.
    Tested

How far pickfit got

macOS arm64

  1. Installs
  2. Starts
  3. 4 of 4 features work
  4. Works offline

Linux x86_64

  1. Installs
  2. Starts
  3. 0 of 4 features work
  4. Works offline

Windows x86_64

  1. Installs
  2. Starts
  3. Main function works
  4. Works offline

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 `&&`.

How to read a tool card

Stitching
pickfit installed this tool itself. Everything under the stitches comes from that run. A tool pickfit has not run never gets stitches.
Verified on your OS
The install steps ran on the system you chose. “Ran on Linux only” means it has not been run on yours yet.
macOS, Linux and WindowsWhere it ran
Green OS marks: pickfit ran the install steps there. Grey ones: the README says it runs there, and pickfit has not tried.
How far the run got
Installs and starts, its main function works, its service answers, it produces model output. A window means a desktop app opened; a plug, an MCP client used it. The mark sits beside the run’s result, under “Why it fits and how we know” and in “How pickfit tested it”.
Visual check
pickfit looked at screenshots of the app. Green: it looks right. Amber with a number: things that look wrong; open it to see them. Grey and dashed: not checked yet.
Known vulnerabilities
Known high or critical vulnerabilities (OSV.dev) in what it installs. Green: none known. Red with a number: how many; open it for the list, and read it before you install. Grey and dashed: not checked, which does not mean safe.
About the run
The day it ran, and the version that ran.
Source of a reason
Every reason a pick fits rests on one profile field. Open the reason to see the field and the value it relies on.
Hidden gem
High quality, little known.
Quality and popularity
Two scores out of 100. Quality: how well it installed and worked when pickfit tried it, and how good its install docs and upkeep are. Popularity: from stars, downloads and Hacker News.
Features checked
Of the main features the README advertises, how many the run actually exercised (green), and how many failed (red). Grey ones were not checked, and the card says why.
Not verified
A well-known tool Fitz mentions from general knowledge. No run record, no steps, no score.